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: Sebastien Metrot <email@hidden>
- Date: Thu, 21 Apr 2005 21:26:10 +0200
May I suggest that your team have a 5 minutes glance at the way project
deps are handled in Visual Studio and CodeWarrior?
<shameless_plug>
For those of you still out of luck with XCode regarding dependencies:
http://machten.blogspot.com/2005/01/xcode-dependencies-workaround.html
</shameless_plug>
Sebastien
Scott Tooker wrote:
Sorry, this is still the model in Xcode 2.0, but we are aware of the
issues the current model has and are investigating ways to improve it.
Scott
On Apr 21, 2005, at 11:11 AM, Andrew Kimpton wrote:
Scott Tooker wrote:
In the current Xcode (1.5), the way that the build style is used
is intended behavior.
OK - I think I found a workaround by adding the library to the extra
linker flags of the bundle target and removing it from the
deployment build style. That way it's not propogated. It also means
that the library is linked in Development builds but nothing calls
it and with improved dead code stripping I guess it will 'fall out'
anyways.
Your statement carries an implication that this style propogation
behvaiour has changed for XCode 2.0 ?
Thanks for the quick response.
Scott
Andrew 8-)
On Apr 21, 2005, at 10:26 AM, Andrew Kimpton wrote:
I have a project which builds a bundle, it in turn includes two
'sub projects' as dependant targets - each a static library of
common code.
It seems like the build style I pick for the 'top level' project
propogates to the sub projects not merely as a 'label' (ie use
the Deployment style from the libblah.xcode project) but as a
concrete set of build options.
This means that a -lxtra_lib flag I specify only in the
deployment build style (using Other Linker Flags) for the top
level target is being passed to the libtool command line of the
two subprojects. I don't want that extra library linked when I
build the two subprojects (aside from the library paths not being
set correctly to find it I don't think libtool allows for a
string of .o files to be combined with another .a archive to
create a new .a archive ?)
Is this a known bug with a workaround ?
Andrew 8-)
_______________________________________________
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