Re: [Config Files] Debugging config files
Re: [Config Files] Debugging config files
- Subject: Re: [Config Files] Debugging config files
- From: Rush Manbert <email@hidden>
- Date: Wed, 01 Mar 2006 14:21:15 -0800
Chris Espinosa wrote:
On Mar 1, 2006, at 11:05 AM, Rush Manbert wrote:
Is there any way to get a dump of the final build setting key/value
pair set? Some way to trace the config file evaluation?
The best practice for this is to add a Run Script Build Phase to the
target, which will dump all the build settings in effect into the log as
env variables.
Thanks. I'll do this.
One other question. Does anyone else think that it would be useful to
be able to do this?:
#include $(myConfigFileName)
I don't see why you need to have a second level of indirection for
config files, when you can just set the Based On on a per-configuration
basis.
Assume that the files debugMultithreadLibSetup.xcconfig and
releaseMultithreadLibSetup.xcconfig are shared between projects,
and ignore pathing issues.
In targetDebug.xcconfig:
librarySetupFile = debugMultithreadLibSetup.xcconfig
#include "projectSetup.xcconfig"
In targetRelease.xcconfig:
librarySetupFile = releaseMultithreadLibSetup.xcconfig
#include "projectSetup.xcconfig"
In projectSetup.xcconfig:
// Setup library names and search paths
#include "$(librarySetupFile)"
// Do other stuff that uses the same boilerplate build settings, with
// different meanings depending on what was included by
// $(librarySetupFile)
Debug Based On = targetDebug.xcconfig
Release Based on = targetRelease.xcconfig
I was thinking I could use this mechanism as a substitute for the lack
of conditionals. There are other methods, and conditionals make them easier.
or to have conditional logic in a config file? They seem to act like
fairly brain dead C header files, but we all know that you can do a
lot with a header file and some conditional logic. I'm thinking of
filing a feature request, but other people may know how to get around
the limitations.
In the future we want to do general conditionals and expansions in the #
logic for config files, but note that even the C++ preprocessor doesn't
even do macro substitution in #include directives at this point.
I realize that variable include file names aren't supported. I'm happy
to hear that you're planning conditional support in config files. It
can't come soon enough!
No feature requests being filed.
Thanks for the answers.
- Rush
_______________________________________________
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