Re: Buildstyles Propogating to sub projects in XCode 1.5 ?
Re: Buildstyles Propogating to sub projects in XCode 1.5 ?
- Subject: Re: Buildstyles Propogating to sub projects in XCode 1.5 ?
- From: Andreas Grosam <email@hidden>
- Date: Fri, 29 Apr 2005 11:03:54 +0200
On 28.04.2005, at 20:48, David Catmull wrote:
On Apr 28, 2005, at 11:21 AM, Andreas Grosam <email@hidden>
wrote:
You can specify in the "Other Linker Flags" setting which library you
want to link against, additionally to those already specified in the
project. That means, do not include the libs libSuperCool respectively
libDebugSuperCool in your project, but use the linker options in the
build styles instead.
For me, this was the biggest reason why it was a problem to have build
styles apply to subprojects. I used this linker flags trick for my
application project, but if I set up dependencies on the library
projects, it caused them to link to their own libraries (which they
couldn't even find because they didn't have the needed search paths).
Yes, thus i would appreciate it if sub-projects would use *their* build
styles - or even better, for each build style in the master project, we
should be able to specify which build style to use for every
sub-project.
And if we would have the option "use master build style", then the
current behavior would still work.
Andreas Grosam
--
David Catmull
email@hidden
http://www.uncommonplace.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
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