[Config Files] Debugging config files
[Config Files] Debugging config files
- Subject: [Config Files] Debugging config files
- From: Rush Manbert <email@hidden>
- Date: Wed, 01 Mar 2006 11:05:55 -0800
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. :-)
One other question. Does anyone else think that it would be useful to be
able to do this?:
#include $(myConfigFileName)
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.
Thanks in advance,
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