If you can build them as static libraries, then good for you. I choose not to amend the makefiles much and use a method that is pretty much standard in Mac OS X "embedded frameworks"

http://developer.apple.com/documentation/MacOSX/Conceptual/ BPFrameworks/Tasks/CreatingFrameworks.html#//apple_ref/doc/uid/ 20002258/BAJJBIEF

Obviously, they are talking amount frameworks here but the same knowledge is applicable to a dyld.
If you have questions about this technique, you can subscribe to Apple's Cocoa mailing list and ask them there. You will probably get a better response about dyld specific questions.


http://lists.apple.com/mailman/listinfo/cocoa-dev

Some people also choose to install them in the standard /usr/local/lib or such. I think Xcode will find them automatically during development but you have to think about what to do during deployment.

Han Ming

On Feb 11, 2004, at 5:21 PM, Mark Goldstein wrote:

The UNIX distributions for Xalan require the Xalan-C++ and Xerces-C++ libraries to be installed as well. I'd like to include the Xalan transformation engine in my Xcode application without requiring the installation of the libraries. Is it possible to build a statically linked version of Xalan that can be included totally within the Xcode project?

Reply via email to