Copyright (c) 2007 The GNU-Darwin Team, plumber <OpenSpecies@gnu-darwin.org> Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. rtool helps to relocate a library as a NeXT/ GNUStep/ Apple Mac OS X Framework bundle. rtool is an "Automator" to relocate a library into a bundle without rebuilding it (including options for other linked Libraries *What means rtool ?* Do Not Touch your Makefile or build scripts. * Relocate libFoo.dylib to Foo.framework ? * Relocate libFoo.dylib to Foo.framework and its dependencies ? * Relocate libFoo.dylib to Foo.framework with a relative path ? * Building My Bundle.app with included Frameworks ? * My libFoo.dylib uses a static sharedir ? sharedir to Resources dir (relative path, identifier, CoreFoundation) - Resources/Examples/share - Resources/Examples/rpath Hacking quickly the libFoo source, build and relocate it after. Apple Framework Programming Guide <http://developer.apple.com/documentation/MacOSX/Conceptual/BPFrameworks/index.html> *Anatomy of a Modern Bundle* The basic structure of a modern bundle is very simple. At the top-level of the bundle there is a directory named Contents. This directory contains everything, including the resources, executable code, private frameworks, private plug-ins, and support files needed by the application or plug-in. While the Contents directory might seem superfluous, it identifies the bundle as a modern-style bundle and separates it from document and legacy bundle types. Apple Bundle Programming Guide <http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFBundles/Concepts/BundleAnatomy.html>