RE: PCH not being used - SOLVED!
RE: PCH not being used - SOLVED!
- Subject: RE: PCH not being used - SOLVED!
- From: Burt Johnson <email@hidden>
- Date: Sun, 22 Jan 2006 19:29:55 -0800
Thanks! That was it! The target had that set to - instead of + for some
reason. I don't _think_ I ever twitched this, but I can't swear for sure
though in all my fudging around...
Or are you saying it is normal for the default to be off? That sounds
pretty bizarre if so. Never heard of an IDE that did it that way...?
Just changed it back to way I had it prior to trying the separate "win.h"
file, and it is now working as expected! That is, lots of errors, but no
longer any complaints about these particular keywords.
Now the real fun begins... :-)
>You have had some bizarre responses asserting that it was somehow
>inappropriate for you to use the PCH file as you have. These
>assertions are erroneous. If they were correct, the PCH system would
>be seriously broken. Anything that you can import/include can be
>incorporated into a pch. It is entirely appropriate to incorporate
>typedefs , #defines, etc. in the pch.
>
>If you will open your TARGET info (double-click the target icon or
>use the Project menu's "Edit Active Target '(target name)'" item),
>select the Build tab, and then type "pref" or "prefix" into the
>search field at right, you should see something like the following:
>
>
>
>Content-Type: image/png;
> x-unix-mode=0644;
> x-mac-hide-extension=yes;
> name="Picture 15.png"
>Content-Disposition: inline;
> filename="Picture 15.png"
>
>Attachment converted: OSX:Picture 15.png (PNGf/ogle) (00180FCC)
>
>In the Configuration popup menu, choose "All configurations", and
>then click the checkbox for "Precompile Prefix Header" until a
>checkmark appears. In the Prefix Header line, type the project-
>relative path of the prefix header -- for a default configuration,
>this would simply be the filename, including extension. In your case
>this would be "FitSync_Prefix.pch".
>
>If your project has somehow lost the Prefix Header, etc. settings,
>they can be added with the "+" button at the bottom of the window.
>Use the GCC names (GCC_PREFIX_HEADER, GCC_PRECOMPILE_PREFIX_HEADER).
>
>TARGET-level setting override PROJECT-level settings.
>
>Your posted fragment of your "FitSync_Prefix.pch" appears to be
>totally valid and appropriate.
>
>Why the default project would not have "Precompile Prefix Header"
>enabled by default is a mystery to me. OTOH, such things can be
>changed. One benefit of the GCC foundation of XCode, it is that just
>about _anything_ can be changed, with some digging. The default
>values for all of the various predefined project types are set by
>specially configured template projects located in "/Library/
>Application Support/Apple/Developer Tools/Project Templates/".
>Modification of these templates is not Apple-supported, but there is
>a fair amount of information available with a little Googling.
>
><http://www.cocoadev.com/index.pl?XcodeProjectTemplates>
>
>-- is a good jumping-off point.
>
>Best of luck on your project.
--
- Burt Johnson
MindStorm, Inc.
email@hidden
http://www.mindstorm-inc.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden