Re: Radar issues (Re: How to file a radar)
Re: Radar issues (Re: How to file a radar)
- Subject: Re: Radar issues (Re: How to file a radar)
- From: Marshall Clow <email@hidden>
- Date: Wed, 19 Jul 2006 20:15:18 -0700
At 9:52 PM -0400 7/19/06, Mike Jackson wrote:
On Jul 19, 2006, at 8:41 PM, Marshall Clow wrote:
At 5:15 PM -0700 7/19/06, Chris Hanson wrote:
On Jul 19, 2006, at 12:58 PM, Ben Weiss wrote:
The lack of support for separate debug/release libraries is
another major headache. I worked with some Apple engineers to
hack around this at the last WWDC, and I'm surprised it hasn't
been addressed yet...
What do you mean by "separate debug/release libraries"?
Well, what _I_ mean is to have two static libraries - a debug
and a release version
and have the release version of my app link against the release
version of the library,
and the debug version link against the debug version.
Usually, the libraries are named "SomeLibrary.a" and
"SomeLibrary Debug.a",
but that's not a hard and fast rule.
Also, I have source files/libraries that I want included in the
debug version, and not at all in the release version.
I tried to follow this thread so I am sure I am just missing
something BUT if you don't fight Xcode then you can very easily have
Debug and Release builds without a lot of work. In fact it is very
little work.
Suppose I have a project that has a base library called "libBase.a",
and an executable that depends on that library.
With you so far - except that I have _several_ executables that
depend on that library.
So setup an Xcode project to build the Library.
So far so good....
Now in the same Xcode project, create a new Target that will be your
executable.
Um, which project? App #1? App #2? App #3? All of them?
Have your executable link against the library that was built in your
first target. Set the executable target to have a dependancy on the
Library. Now, when you set the build type to "Debug" then Xcode will
make sure that Library is built with the Debug settings and place
the built library in {XcodeBuildLocation}/Debug/libBase.a and place
the executable in {XcodeBuildLocation}/Debug/MyApp.exe
When you are ready for a Release version simply change the build
type to "Release" and build. The base lib will be built in release
mode, the executable will be built in Release mode, and both will be
place in {XcodeBuildLocation}/Release/.
How much simpler can this possibly be. On other systems you have to
do weird things like naming each built product with "_debug.a" or
some other weird things. Xcode will do the right thing with release
and Debug. You just have to make the project dependancies for it to
work.
That sounds perfectly reasonable, except for the idea that there's
one library and one application.
[ The situation is moderately complicated; there are currently 3 apps
and 4 libraries ]
--
-- Marshall
Marshall Clow Idio Software <mailto:email@hidden>
It is by caffeine alone I set my mind in motion.
It is by the beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
_______________________________________________
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