Compiling error on xcode 1.5

#1 Raymond, did you follow the docs exactly? It looks like you may not be setting your paths correctly in XCode. Please let me know if you've followed the instructions exactly. :)

Regarding the locked / unwritable error.. this can cause problems too, and I'm not sure why your project or files would be locked. If you can, ensure that read&write access is granted for all the files in the project, and the project itself.

#2 Yes I did follow the instruction step by step :-),

I also upgraded the build targets to native per xcode help files. converting PB project to xcode and got one error

Building target "Torque-MacCarb-Debug (Upgraded)" with build style "Development" (optimization:level '0', debug-symbols:on) (1 error)

Trying to read more about this xcode compiler.

Right now I have one error (mentioned above) and still can not save because of the file is locked or unwrittable.

#3 I have never converted the targets to native XCODE from the PB targets and my side compiles fine (after ranlib'ing the vorbis .a files). Not sure if this affects you.

I am assuming you downloaded the SDK rather than checked out from CVS. I am not familiar with that installer so I may be off here as i usually work off of the cvs HEAD.

Maybe this helps. Good luck and keep at it!

#4 Compiled the sdk using VC++6.0 on the windows machine and no errors. Now I have 7 errors with xcode.

I do have a codewarrior for mac. maybe I should try this one but cannot find documentation on how to compile the sdk for codewarrior or maybe I just need to take a little break.

see what happens...

#5 Hey Raymond,

gonna tell you a story. I was a Mac user back before the discovered America, around System 6. Then I somehow got into VMS and Fortran and later into TRS-80 and PCs and the everything got complicated.

Now I try to get a grip on Torque on the new Macs, which are now Unix system with a Mac attitude. If I were a cynic I would say worst of both worlds.

But after all - it's a great system! But when you try to get under the hood, things can get rough.

Tell you what, I am going to do the compile myself as soon as I can (might be next weekend).

So don't get frustrated. I think the Mac community needs more attention (because cross platform compatibility is _THE_ #1 reason to buy TGE), so it needs everyone's help.

So I'll be back with an answer as soon as I can - if I can.

#6 @Dirk

This has nothing to do with the original thread, but I really agree with you.
Panther is the system where things began to get back in place. Jaguar was only useable and everything else before it just sucked compared to 9.

Ooops, I meant @Dirk not @Raymond

#7 Raymond, it sounds like maybe something got clobbered when you converted the projects to native XCode. I'm not sure, but typically we don't see these problems with compiling the TGE code on Mac. If you follow the instructions step-by-step, it should work like a charm.

You might try re-downloading to a new folder and not converting the project yet. See if it compiles under the default settings first.. then you'll know for sure where any problems in the future are introduced.

#8 I got it to compile now with 2 errors and 1 warning.
I was also able to save the compiled code.

All I did is un stupid myself .

@ Josh,
The folder, I was building straight from the disk image that's why xcode can not save and properly compile the sdk.

My errors now is about:

ld: table of contents for archive: ../lib/vorbis/macosx/libogg.a is out of date; rerun ranlib(1) (can't load from it)

ld: table of contents for archive: ../lib/vorbis/macosx/libvorbis.a is out of date; rerun ranlib(1) (can't load from it)

and the warning:

ld: warning prebinding disabled because dependent library: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices can't be searched.

As soon as I fix the vorbis everything should run okay.
Need to find out about that warning.

@Dirk,
I used to monkey around with attari 400 then tandy 8080, went mac then pc now back to mac with pc still on my hip. :-)

#9 You can fix the vorbis issue by:

open terminal and enter:

cd YOURTGEPATH/lib/vorbis/macosx/
ranlib *.a

That should do it!

#10 Right, I forgot there was this ressource.