Re: Re: Re: Best approach for customized project templates?
Re: Re: Re: Best approach for customized project templates?
- Subject: Re: Re: Re: Best approach for customized project templates?
- From: "Jim Thomason" <email@hidden>
- Date: Wed, 27 Sep 2006 13:00:31 -0500
Ah ha, I got it. The problem was very subtle.
Apparently, I had previously clicked on and turned on warnings at the
project level. I then unchecked it and was trying to get my config
file to work.
Alas, I had now overridden it at the project level and was SOL - since
that trumped the config. For those that were unaware, I figured out it
was overridden by the fact that the text was in bold.
Solution? Click on the offending item (treat warnings as errors in
this case) and hit delete. That removes the bold text so it goes back
to inheriting whatever it had before. It then properly inherited from
my config file.
So Ishould be good to go.
-Jim....
On 9/27/06, Jim Thomason <email@hidden> wrote:
I finally got around to trying to implement an .xcconfig file and am
either missing something or it doesn't work quite how I'd expected.
I've been over the docs on building config files a half a dozen times,
and I think I'm following 'em.
Basically, I can set some things sometimes, but not always. For
instance, if I base my project settings off of this config file, it
completely ignores my note to treat warnings as errors (but, for
example, acknowledges the zero link setting). But if I base my build
settings off of this config file, it completely ignores my note to
shut off zero link (but, for example, acknowledges the warnings
setting).
So...what do I do? Do I just need to add the same xcconfig file to
both places? It seems kinda silly, but I can cope if that's what I'm
supposed to do. But since it only acknowledges some things some of the
time, I don't know if that's even a valid approach.
What's my next step?
Thanks,
-Jim....
For sake of argument, this is my file:
PREBINDING = YES
ZERO_LINK = NO
LINKER_DISPLAYS_FILES_FOR_UNDEFINED_SYMBOLS = YES
INFOPLIST_PREPROCESS = YES
GCC_ENABLE_OBJC_EXCEPTIONS = YES
GCC_PRECOMPILE_PREFIX_HEADER = YES
GCC_TREAT_WARNINGS_AS_ERRORS = YES
GCC_WARN_ABOUT_MISSING_PROTOTYPES = YES
GCC_WARN_ABOUT_RETURN_TYPE = YES
GCC_WARN_TYPECHECK_CALLS_TO_PRINTF = YES
GCC_WARN_INITIALIZER_NOT_FULLY_BRACKETED = YES
GCC_WARN_CHECK_SWITCH_STATEMENTS = YES
GCC_WARN_UNUSED_VARIABLE = YES
GCC_WARN_SHADOW = YES
GCC_WARN_FOUR_CHARACTER_CONSTANTS = YES
GCC_WARN_SIGN_COMPARE = YES
GCC_WARN_ABOUT_MISSING_NEWLINE = YES
GCC_WARN_ALLOW_INCOMPLETE_PROTOCOL = YES
On 8/27/06, Greg Guerin <email@hidden> wrote:
> Jim Thomason wrote:
>
> >Ideally, I'd just like some way to say "keep these options enabled in
> >all projects".
>
> See:
> <http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeUserGuide/Contents/Resources/en.lproj/05_05_build_configs/chapter_33_section_6.html>
>
> And:
> <http://developer.apple.com/tools/xcode/xcodebuildsettings.html>
>
>
> Also see this past thread for some caveats:
> <http://lists.apple.com/archives/xcode-users/2006/Jul/msg00688.html>
>
> And see the Xcode 2.4 release notes for when bugs were fixed:
> <http://developer.apple.com/releasenotes/DeveloperTools/Xcode/Xcode.html>
>
> -- GG
>
>
> _______________________________________________
> 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
>
_______________________________________________
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