[Apocalypse]

Hello,
I am having a large problem with compiling on OS X final. I saved some source code when I went from PB to X on another partition. Once the reformat and installation was complete, I copied the source back to my X partition. The only problem is that I setup the project path as a subdirectory of what it had been before and I put the project in there (before I had used $HOME, now I use $HOME/Development Projects). My source will not compile now. It can't find any of the outlets so ever function that I call defaults to id and doesn't do anything. I thought that I had corrected the problem a few days ago when I disabled header maps yet the problem returned yesterday. After toying with it for an hour or two I gave up (it was 1 AM and I had to be at work today).
I think that there is a path problem and it could be fixed by re-writing the whole project (new project, rebuild NIB, then copy the source over) but I would like to avoid that (I fear that I may forget something).

If anyone can help, please respond! I am dead in the water without a functioning compiler!!!

[Dalgo]

Okay, I don't really know anywhere in Project Builder where the path of the project directory should matter. I move projects around all of the time and it doesn't matter so there are three things that you could do:

1. In order to rule out a path problem make a symbolic link to the file in your home directotry or just move the thing into your home directory and see if it'll work.

2. If All of your files are now red in Project Builder it isn't too big a deal. There seems to be something wrong with this version of project Builder such that it can never seem to find two of my classes even though I never move them. Solution? Just delete the red things which have no file backing them and drag and drop the actual file back into the project builder window. Unless you have like 200 files this isn't too much of a pain.

3. Check to see if a path problem is really the reason why stuff won't work. When I first tried to compile a project under OS X final that compiled perfectly under the beta it failed. The reason was that for some reason it looked like it was automatically linking against Quickdraw.h. The problem was that I had defined a structure called RGBColor and there was a similar one defined in Quickdraw.h. For some reason I couldn't just delete my definition and use theirs. I don't know why theirs didn't work. It looked like the same definition that I had. Anyway, I just renamed all occurrences of my structure and it compiled fine.

[Dalgo]

Okay, I don't really know anywhere in Project Builder where the path of the project directory should matter. I move projects around all of the time and it doesn't matter so there are three things that you could do:

1. In order to rule out a path problem make a symbolic link to the file in your home directotry or just move the thing into your home directory and see if it'll work.

2. If All of your files are now red in Project Builder it isn't too big a deal. There seems to be something wrong with this version of project Builder such that it can never seem to find two of my classes even though I never move them. Solution? Just delete the red things which have no file backing them and drag and drop the actual file back into the project builder window. Unless you have like 200 files this isn't too much of a pain.

3. Check to see if a path problem is really the reason why stuff won't work. When I first tried to compile a project under OS X final that compiled perfectly under the beta it failed. The reason was that for some reason it looked like it was automatically linking against Quickdraw.h. The problem was that I had defined a structure called RGBColor and there was a similar one defined in Quickdraw.h. For some reason I couldn't just delete my definition and use theirs. I don't know why theirs didn't work. It looked like the same definition that I had. Anyway, I just renamed all occurrences of my structure and it compiled fine.

[Apocalypse]

I ended up finding the solution and it had nothing to do with the path after all. It appears as though the Project Builder with the Public Beta either defaulted all functions to int or was just very leniant about what you claimed return types would be.

It appears as though this release of Project Builder will only allow functions that it cannot find (those residing in other files/classes) to default to id. I only actually was receiving one error in my compile when I try to execute a switch statement with a function as a parameter. If I had first read the function's return into an integer that would have been ok but I ended up casting it and everything worked fine. All my other problems were just warnings of things that it "couldn't find"

Thanks for your suggestions, though.
Jeff.