On Oct 30, 2007, at 16:44:33, Chris Espinosa wrote:
Two ways to gather more data:
1) Add -v to the Other C Flags build setting and rebuild the file
that can't find the #include. Copy the build transcript and save it
in a new text file. Then switch Active Architecture to Intel and
rebuild. Compare the two transcripts. If the compiler's search
paths are different or missing, you'll see why.
2) Select the file, set Active Architecture to i386, and
preprocess. Save As... on the preprocessed file. Then switch
Active Architecture to ppc and preprocess again. Compare the two
files and see whether the #included file was defined out in some way
or place.
The only things that come to mind are:
- the source conditionally #includes the file based on architecture
- the source conditionally defines the #included file's include
guard based on architecture
- the header is in an architecture-specific path that's not being
found by the ppc side (least likely)
I opened the project this morning and built. Today it found the
#included file just fine. Must've been something wanky going on in
Xcode yesterday. The project hasn't changed since 2.4 (other than
opening it in 3.0 - it's still set to be a 2.4 style project). There
are no arch-specific #includes in the files that was generating the
error. Oh well, as long as it now works.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
