Re: XCode 2.1 issues & fixes
Re: XCode 2.1 issues & fixes
- Subject: Re: XCode 2.1 issues & fixes
- From: Scott Tooker <email@hidden>
- Date: Mon, 13 Jun 2005 18:21:17 -0700
On Jun 13, 2005, at 5:16 PM, Tom Harrington wrote:
I've solved a couple of problems I had with XCode 2.1; I though I'd
get them into the list archives, since I don't see them documented
anywhere yet. The following both relate to things that worked in one
project since sometime in 2002, up through XCode 2.0, but caused
trouble with 2.1.
1. Build Style Names
If your build style name has a comma in it, rename it to something
else. You'll save yourself some headaches, because this seems to
confuse the hell out of XCode 2.1. The error message was something
like "output file specified twice", though that was obviously not
correct (as a quick look at the gcc command line showed). (my build
styles had been things like "Deployment, Foo" and "Deployment, Bar",
which differed in some settings, in case you're wondering).
Please file a bug on this. We should do validation of the
configuration name.
2. Derived source code
I have a build stage that generates a .m/.h pair of files, which later
get compiled. First XCode 2.1 couldn't find the header; after adding
an explicit header search path, XCode couldn't find the .m file to
compile it. It wasn't a huge mystery why; the command XCode was
giving to gcc referenced a nonexistent path.
What finally fixed the problem was opening up the info window for the
files and switching the path type to absolute. I had been using a
build-relative path here. I don't know why this was a problem; the
derived sources were put right into $DERIVED_SOURCES_DIR, as read from
the deriving process's environment, but still XCode 2.1 couldn't find
them.
File a bug on this too, absolute path references are (for the most
part) usually not what you want. The build relative path should work.
that it doesn't is a bug.
Scott
BTW the above stumped no less than 4 Apple engineers last week at
WWDC. :-)
On the same file: When moving from one machine to another, the "file
type" for the derived ObjC file, as shown in the inspector, was for
some reason changed from "sourcecode.c.objc" to "file". This resulted
in XCode thinking it didn't know what to do with the file, and
therefore not compiling it. Switching this back seems to have fixed
things.
--
Tom Harrington
email@hidden
AIM: atomicbird1
_______________________________________________
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