Re: Including different libs based on build style
Re: Including different libs based on build style
- Subject: Re: Including different libs based on build style
- From: Scott Tooker <email@hidden>
- Date: Wed, 25 Aug 2004 21:23:10 -0700
Nope, the inability to indicate files to include/exclude at the build
style level is a known problem.
Scott
On Aug 25, 2004, at 2:59 PM, Brad Oliver wrote:
On Aug 25, 2004, at 2:37 PM, email@hidden wrote:
The only way I've been able to do this is with two separate targets
and
to add both versions of the files to the project. The targets are
exactly the same except for which version of foo.a and bar.a they
reference. This seems like serious overkill and complicates
maintenance
(now have to do things to multiple targets when making changes).
Let me add a "me too". I ended up going the multiple-target approach
and ditching build styles entirely because I couldn't find a way to
resolve this. Build styles seem cool up until the point where you need
to have different files in your debug and release targets. Since that
is typically the case with the projects I work on, the utility of
build styles is, for me, negligible unless there is some solution to
this that I'm misunderstanding.
--
Brad Oliver
email@hidden
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.