PDA

View Full Version : Problem Updating Old Xcode Projects


dancedrummer
2006.04.10, 02:55 PM
I recently moved up to Xcode 2.2.1 and am getting this error when I try and compile my projects from 1.5:

INTERNAL ERROR
File: /SourceCache/DevToolsBase/DevToolsBase-660/pbxcore/FileTypes/../PBXFileType.m
Line: 493
Object: <PBXFileType:0x0130e170>
Method: subpathForWrapperPart:ofPath:withExtraFileProperti es:

path should be a non-empty string, but it's an empty string

then ultimately i get this error:

No launchable executable at present path.

Thanks in advance for any info you can share.

dd

szymczyk
2006.04.10, 05:13 PM
Clean all your targets and rebuild your project. If that doesn't fix the problem, the project upgrade from 1.5 to 2.2.1 had problems. Delete the .xcodeproj project file and update the old .xcode project file again.

If those two suggestions don't work, you may need to just create a new Xcode project.

dancedrummer
2006.04.11, 03:23 PM
Thanks Mark.

I cleaned all targets, tried just clicking through, etc. to no avail. The only solution appears to be creating a new project and rebuilding it. :(

There does appear to be a number of people who have run into this that I found on various other threads. Specifically this happens upgrading the ide from x to 2.2.

DoG
2006.04.11, 03:34 PM
Have you tried upgrading your target from legacy?

dancedrummer
2006.04.11, 08:32 PM
Yup. When I rebuild the project with Xcode 2.2 it will only compile using the "Release" build style, Debug gives me a "BAD_ACCESS_EXC" code in the debug console and the app won't run. Only one of my apps does this.

dancedrummer
2006.04.12, 07:01 PM
Sorry if this isn't the most appropriate place. It's where it started. :)

This appears to have been a bug or at least a short coming in memory management that the new debug build style flagged as suspect. If anyone can direct me to the proper place to discuss or shed some light that would be great, at any rate I don't want to leave this hanging as is.

I was creating two arrays:

tbossnums = [[NSArray alloc] initWithObjects:@"0",@"1",@"2",@"3",@"3",@"4",@"4",@"4",@"5",@"5",@"5",@"6",@"6",@"6",@"6"];
tcolornums = [[NSArray alloc] initWithObjects:@"0",@"2",@"2",@"2",@"3",@"2",@"3",@"4",@"3",@"4",@"5",@"3",@"4",@"5",@"6"];

Solved it by constructing them a bit differently:

NSString *tbossnumstring = @"0,1,2,3,3,4,4,4,5,5,5,6,6,6,6";
NSString *tcolornumstring = @"0,2,2,2,3,2,3,4,3,4,5,3,4,5,6";
tbossnums = [tbossnumstring componentsSeparatedByString:@","];
tcolornums = [tcolornumstring componentsSeparatedByString:@","];

Kinda drives me nuts to have to have to create a string and then parse it into an array. I'm still a newbie to this stuff . . . .

Nortie
2006.04.13, 01:36 AM
tbossnums = [[NSArray alloc] initWithObjects:@"0",@"1",@"2",@"3",@"3",@"4",@"4",@"4",@"5",@"5",@"5",@"6",@"6",@"6",@"6"];



You will want the -initWithObjects to end with nil -> [[NSArray alloc]initWithObjects:@"0",@"1",@"2",nil];

dancedrummer
2006.04.13, 02:20 PM
Thanks Nortie!