Xcode Not Building

by TheOneEyed Hobo on 02/18/2007 02:07, 25 messages, last message: 03/03/2007 23:17, 4584 views, last view: 05/04/2024 18:49

Whenever I try open Sauerbraten with Xcode, I get an error that says \\\"The application g++-4.0 quit unexpedtedly


EXC_BAD_ACCESS (0x0001)
KERN_PROTECTION_FAILURE (0x0002) at 0x00000e73

Thread 0 Crashed:
0 0x1000 + 11360
1 0x1000 + 4300
2 0x1000 + 3536\\\"

Then, when I try to build it gets an error that says \\\"Command /sur/bin/g++-4.0 failed with exit code 10\\\" I have tried this on two computers and the exact same thing happens, so it\\\'s not a problem with my g++ file, but with the source.

Thanks,
The One-Eyed Hobo

   Board Index   

#6: Re: ..

by Greywhind on 02/18/2007 16:45, refers to #2

g++ is actually used by XCode as the compiler. XCode is just an IDE built on top of it. So getting a g++ error is reasonable.

I used XCode until I decided my current project would be cross-platform, at which point I switched to command-line gcc for easier porting to Linux.

Anyhow, perhaps Hobo's XCode has gcc 4.0 rather than 4.0.1? If so, I suppose he could try to update XCode.

reply to this message

#7: ..

by SanHolo on 02/19/2007 10:17

I wanted to Test this and got sauerbraten from CVS just some minutes ago. Here is what I get when I try to open the file sauerbraten.xcodeproj:

"Project [...]/sauerbraten.xcodeproj cannot be opened because the project file cannot be parsed."

OS X 10.4.8
XCode 2.4.1
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5367)

reply to this message

#8: ..

by SanHolo on 02/19/2007 11:10

OK, I deleted the CVS-directory on my machine, re-downloaded everything and all goes well. There is one warning, but the compilation did not fail and sauer runs good.

The grass looks awesome on nmap8_d (which got some minor but great alterations), framerate drops from ~160 to ~90 in grassy locations though.

reply to this message

#9: ..

by absinth on 02/19/2007 18:50

i was e-mailed about this "issue" and so i will reply here.

first, your posts contradict each other, one tells us this happens only on one machine (but works fine on the other), the other tells us this happens on all (?) machines.

second, what DMG file are you talking about, or where did you get the source (and which version) from? are you trying to build directly from the source included in the mac distribution DMG file? i think building directly from the mounted DMG would be a bad idea in any case.

third, i really think you should just re-install Xcode, and update to the latest version, which is 2.4.1. obviously there is something wrong with your install since no one else has this problem.

reply to this message

#10: ..

by Der/Nalia on 02/21/2007 13:31

try switching your build mode to Development, instead of any of the Deployments... Unless you really know Xcode, anything other than the default Development Build Phase can lead to problems.

reply to this message

#11: ..

by The OneEyedHobo on 02/24/2007 15:42

I mounted the Mac DMG, opened it, selected all the files, and copied them into a folder on my Desktop called Sauerbraten. Then, I used the source from there. If that is not what I should be doing, please direct me to the source for Mac.

Thanks,
TheOneEyed Hobo

reply to this message

#12: ..

by absinth on 02/24/2007 19:41

>Then, I used the source from there
sounds fine

>please direct me to the source for Mac
of course you can always use CVS to get the latest sources too

reply to this message

#13: ..

by SanHolo on 02/25/2007 11:56

Yeah, use CVS.

- Open your Terminal
- CD into your desired Sauerbraten Directory (e.g. ~/Programming/sauer_cvs/)
- enter the two CVS-commands provided on sourceforge to get all the files
- When done, open the .xcodeproj-File

That's how it works for me.

reply to this message

#14: ..

by Hidden on 03/01/2007 01:18

What account name and pass do I use for the CVS?

reply to this message

#15: Re: ..

by SanHolo on 03/01/2007 11:01, refers to #14

user "anonymous" and an empty pass.

reply to this message

#16: Re: ..

by Drakas on 03/01/2007 19:11, refers to #14

maybe read in sf.net/projects/sauerbraten/ ?

reply to this message

#17: ..

by . on 03/02/2007 22:51

Okay, I got the thing to download, but it isn't getting the xcode or vcpp folder! It says "Updating sauerbraten/xcode/sauerbraten.xcodeproj" or something like that, and the same with sauerbraten/vcpp/whatever, but it doesn't put them into my system. I've tried running searches (it's not on the hard disk at all, and not hidden or anything), and specifically saying "sauerbraten/xcode", but nothing works!

Thanks,
TheOneEyed Hobo

reply to this message

#18: ..

by . on 03/02/2007 22:53

Also, it's in the "src" folder, but there are different files in there; it's not the same one. I think that part of it may be that the frameworks are missing, which they are because they are only found in that folder.

reply to this message

#19: ..

by absinth on 03/02/2007 23:39

you must use the -P option like it is explained on the sourceforge site. -P prunes old files that aren't used anymore, like the xcode folder in sauerbraten. the xcode folder in src/ is the one to use

reply to this message

#20: ..

by absinth on 03/02/2007 23:39

you must use the -P option like it is explained on the sourceforge site. -P prunes old files that aren't used anymore, like the xcode folder in sauerbraten. the xcode folder in src/ is the one to use

reply to this message

#21: ..

by Der/Nalia on 03/03/2007 03:03

hey... try reinstalling Xcode... you can download it at

http://developer.apple.com/tools/download/

its a big download... I pray you have high speed

reply to this message

#22: Re: ..

by SanHolo on 03/03/2007 09:59, refers to #21

His problem is not Xcodes fault but his own. He fails to use CVS correctly.

reply to this message

#23: ..

by absinth on 03/03/2007 14:00

>His problem is not Xcodes fault but his own

the original post (about gcc crashing) certainly indicates an damaged or old xcode version too

reply to this message

#24: ..

by ßlkfd on 03/03/2007 22:51

Then, how do I use CVS correctly? Besides, it's a g++ error, not a gcc error. The C files work fine.

reply to this message

#25: ..

by absinth on 03/03/2007 23:17

g++ is gcc

reply to this message

   Board Index