Re: Linking against a non-Framework
Re: Linking against a non-Framework
- Subject: Re: Linking against a non-Framework
- From: Markus Hitter <email@hidden>
- Date: Wed, 11 May 2005 08:44:19 +0200
Am 11.05.2005 um 07:35 schrieb Daniel Harple:
I am using libpng (not installed on vanilla mac boxes) in one of my
projects. I have added a copy files build phase that copies over the
libpng dylib and headers into the Frameworks folder, but when I start
the application on my test box without libpng, the application
searches in /usr/local/bin for it.
One unfortunate issue with dynamic libraries (, bundles, frameworks) on
Darwin/Mac OS X is, they have their installation path compiled into the
binary.
What is the correct way to include a non-Framework in your application
bundle?
Set the installation path to "@executable_path/...." and embed it like
a framework? I didn't test it, but it's the way recommended for
embedded frameworks. See Xcode documentation.
I have tried several different methods.
Since you have to ship the library with your app anyways, how about
linking against the static version libpng.a instead of embedding the
dylib? This would allow you to do dead code stripping as well.
Hope that helps,
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden