Re: Other linker flags
Re: Other linker flags
- Subject: Re: Other linker flags
- From: Dieter Oberkofler <email@hidden>
- Date: Mon, 19 Jan 2009 16:26:39 +0100
Actually it is quite simple: my app uses a few 3rd party libraries
that are available in different "builds" (Stable, Unstable,
Development, etc.). My XCode project uses several resources (static
libraries, includes, binaries, etc.) and it should be made as simple
as possible to switch between the different "build". Each build has
it's own root directory and currently I simply define a new setting in
the Project settings and use this environment variable (${A_ROOT_DIR})
as the prefix when specifying where the headers, libraries or binaries
are.
Thank you,
Dieter
On 19.01.2009, at 15:31, Chris Espinosa wrote:
On Jan 19, 2009, at 9:21 AM, Dieter Oberkofler wrote:
Is there away to make XCode check the dependencies of libraries
linked using the "Other linker flags" section in the "Linking
Settings" of XCode 3.1.2?
I know that when specifying the "Link binary with Libraries"
Section of "Groups & Files" the dependencies are checked but then I
seem unable to use an arbitrary library path specified as an
environment variable.
Try specifying a Source Tree (Xcode > Preferences > Source Tree)
based on the environment variable, then add the library Relative to
Source Tree. You may still need to provide a Library Search Path so
the linker can find the library, but this may help Xcode in its
dependency checking.
I assume that what you're doing is building some dylib in an
interesting place (like /usr/local/lib or something like that) and
updating it, and you want Xcode to notice and re-link your app when
you do?
Chris
_______________________________________________
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