Re: [Config Files] Debugging config files
Re: [Config Files] Debugging config files
- Subject: Re: [Config Files] Debugging config files
- From: Chris Espinosa <email@hidden>
- Date: Wed, 1 Mar 2006 13:15:27 -0800
On Mar 1, 2006, at 11:05 AM, Rush Manbert wrote: Does anyone have any slick suggestions for config file debugging? I need to develop a set of config files that we will use for all of our development, allowing for company-wide policies, project-scope policies, target-scope policies as defined by the original developer of a project, and local overrides for test and debug. All the usual stuff.
I've got a simple project that I'm using to figure out what I can and cannot do, but the only way that I know to determine whether my web of config files is working correctly is to examine the compiler and linker command lines that Xcode generates. That's rather indirect.
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? I'm also looking for any pointers from people who have done this already about how to organize a config file hierarchy. (I saw the one a few days ago about including a possibly-nonexistent file to limit the architecture. I'm going to use that.)
And if I've missed something in the documentation or archives, RTFM is an acceptable answer. :-)
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. 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. 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.
Chris |
_______________________________________________
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