Re: Debug and Release llibraries
Re: Debug and Release llibraries
- Subject: Re: Debug and Release llibraries
- From: Paul Walmsley <email@hidden>
- Date: Wed, 19 Oct 2005 17:00:34 +0100
Maybe so, but that's been standard practice in Unix/Makefile
environments for years...
But that's exactly Caerwyn's point.
xCode is not a unix make file! It is a GUI IDE! Best practice should
not involve passing linker flags.
There may well be other ways to do this in the current version of Xcode,
with configurations or custom targets, but the last time I tried it (in
1.8 I think) the only way was using good old linker flags. My point was
that specifying libraries as arguments to a linker has been a standard
way of doing things for many years to a large number of people, although
Codewarrior veterans are likely to throw up their hands in horror.
While it would be great to have a situation where the IDE was totally
insulated from the underlying toolset I think this is unrealistic with
C++. Or at least where you've got a situation where you have to deal
with frameworks, multiple OS SDKs, universal binaries, zero-link,
dynamic libs, etc. Coding in C++ is always going to a be a
flying-by-the-seat-of-your-pants experience when you have to take all
these things into account. Each compiler/linker toolset has its own
quirks and I don't think you can take on non-trivial projects without a
reasonable understanding of how everything slots together under the hood.
Caerwyn wrote:
it doesn't make life easier for those who come from Windows or CodeWarrior
You're right. It doesn't. See, we agree on some things :-)
Paul
_______________________________________________
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