TGE MacOS X 10.5 compatibility
by Mathieu · in Torque Game Engine · 10/24/2007 (6:21 am) · 22 replies
Does anyone tried to run TGE 1.5.2 on Beta builds of Leopard?
About the author
Developer at frogames.com / frogames.net
#3
10/28/2007 (9:00 am)
Compiled 1.5.1 with XCode 3 on Leopard today without a hitch. My game seems to run as before, and the log doesn't show any errors or warnings. I think we are safe with this update.
#4
10/28/2007 (10:35 am)
Thanks a lot for your feedback Miguel!
#5
I haven't had a chance to try it myself yet, but the early developer seeds worked without a hitch.
/Paul
10/29/2007 (11:56 am)
Thanks Miguel! I haven't had a chance to try it myself yet, but the early developer seeds worked without a hitch.
/Paul
#6
10/30/2007 (7:30 pm)
Can't run the installer for TGE.
#7
Bleh :-(
11/09/2007 (4:50 am)
Hmm, if anyone's been trying to use it under X11 (I have my reasons dammit), you'll find that SDL doesn't work on Leopard yet.Bleh :-(
#8
The http://www.nabble.com/SDL-not-building-on-OS-X-10.5-(Leopard)---t4697168.html
The old gcc will also be installed if you use the 10.3.9 SDK from XCode custom installation
11/09/2007 (6:58 am)
Have you tried linking against 10.3.9 SDK? It seems SDL is linking against now deprecated CoreAudio methods.The http://www.nabble.com/SDL-not-building-on-OS-X-10.5-(Leopard)---t4697168.html
The old gcc will also be installed if you use the 10.3.9 SDK from XCode custom installation
#9
Gary (-;
PS Lally, there's lots of good reasons to do it. I did it a while go, ref1, ref2. Among others, at least you get working joystick input this way :-)
Actually, I'm curious as to whether you've encountered problems with leopard's newfangled X11. The new stuff is awesome in theory [magical transparent X server stuff], but in practice it's a bit of a clusterf**k. [try connecting to a remote host enabling Xforwarding, as a way to launch apple's X11, then watch Xquartz's CPU usage.]
11/09/2007 (6:19 pm)
I have fink's SDL working just fine on leopard, here. No idea if the audio is causing problems, but with the latest of everything it seems to work fine.Gary (-;
PS Lally, there's lots of good reasons to do it. I did it a while go, ref1, ref2. Among others, at least you get working joystick input this way :-)
Actually, I'm curious as to whether you've encountered problems with leopard's newfangled X11. The new stuff is awesome in theory [magical transparent X server stuff], but in practice it's a bit of a clusterf**k. [try connecting to a remote host enabling Xforwarding, as a way to launch apple's X11, then watch Xquartz's CPU usage.]
#10
I've been trying to get TGE 1.5.2 compiled under Leopard using XCode 3. First I encountered that the sdk 10.3.9 directory on a freshly installed Leopard doesn't exist anymore. I changed all occurences of that string to the newest 10.5 directory under /developer/SDKs/.
But now the compiler breaks in the file macCarbFileio.cc at line 57 saying that "utimes was not declared in this scope". This is the line:
return( utimes( path, NULL) == 0); // utimes returns 0 on success.
Any idea about this error? Does someone know if I made it right changing all directories from 10.3.9 to 10.5?
Martin :-)
11/14/2007 (12:46 pm)
Hey guys,I've been trying to get TGE 1.5.2 compiled under Leopard using XCode 3. First I encountered that the sdk 10.3.9 directory on a freshly installed Leopard doesn't exist anymore. I changed all occurences of that string to the newest 10.5 directory under /developer/SDKs/.
But now the compiler breaks in the file macCarbFileio.cc at line 57 saying that "utimes was not declared in this scope". This is the line:
return( utimes( path, NULL) == 0); // utimes returns 0 on success.
Any idea about this error? Does someone know if I made it right changing all directories from 10.3.9 to 10.5?
Martin :-)
#11
You must run it and check appropriate missing SDKs I think.
I *only* upgraded my system, so the 10.3.9 sdk is already there.
let me know if it sounds right. 8-)
11/14/2007 (12:53 pm)
@Martin: there is an optionnal install on the XCode part of the CD/DVDYou must run it and check appropriate missing SDKs I think.
I *only* upgraded my system, so the 10.3.9 sdk is already there.
let me know if it sounds right. 8-)
#12
But why does it still need then 10.3.9? Is that the "lowest" OS version it would run then with it? I don't really understand why TGE wants such an old sdk version.
11/14/2007 (1:05 pm)
Aha! Ok, thanks. But why does it still need then 10.3.9? Is that the "lowest" OS version it would run then with it? I don't really understand why TGE wants such an old sdk version.
#13
11/14/2007 (1:10 pm)
From my understanding (I can be completely wrong), it should ensure compatibility with previous versions of Os X (10.3, 10.2).
#14
11/15/2007 (1:30 am)
Ah ok, sounds logical. So if I would put in 10.4 I would ensure it's downward compatible to 10.4 Tiger versions of OS-X?
#15
There is still a base of users with 10.2 and 10.3 systems.
Don't forget Mac users are keeping there machine much more longer than PC ones.
I still own my outdated Performas machine with Os 8. 8-)
One is more than 10 years old. ;-)
11/15/2007 (1:41 am)
Yes, but nothing before that version.There is still a base of users with 10.2 and 10.3 systems.
Don't forget Mac users are keeping there machine much more longer than PC ones.
I still own my outdated Performas machine with Os 8. 8-)
One is more than 10 years old. ;-)
#16
I'll try to install tonight the missing 10.3.9 directories to see if that works then. I'll get back then here if it worked. But thanks so far Stephan!
11/15/2007 (1:54 am)
Ok, that is definately a strong argument! :-)I'll try to install tonight the missing 10.3.9 directories to see if that works then. I'll get back then here if it worked. But thanks so far Stephan!
#17
Put in the Leopard DVD and start the package
Leopard DVD -> Optional Installs -> XCode Tools -> Packages -> MacOSX10.3.9.pkg
and make sure you select the path to install to is the /Developer/SDKs directory and not the root directory and voila you have the missing 10.3.9 sdk!!
In the same source path you find also the gcc-3.3 package which you need to install too. The destination directory is selected automatically, so don't change it.
My build just succeeded! Yay! Thanks a lot! :-)
11/15/2007 (1:14 pm)
Hah! Stephan, you were right! It's quite simple:Put in the Leopard DVD and start the package
Leopard DVD -> Optional Installs -> XCode Tools -> Packages -> MacOSX10.3.9.pkg
and make sure you select the path to install to is the /Developer/SDKs directory and not the root directory and voila you have the missing 10.3.9 sdk!!
In the same source path you find also the gcc-3.3 package which you need to install too. The destination directory is selected automatically, so don't change it.
My build just succeeded! Yay! Thanks a lot! :-)
#18
11/15/2007 (1:45 pm)
You are welcome Martin! 8-)
#19
Thx
06/22/2008 (7:06 pm)
Oh for the love........I cannot get this stinking utimes error to go away. I have the 10.3.9, 10.4u and 10.5 sdk's installed and ready. As for the project settings I have toggled the base sdk between the different sdk's and I keep getting the same error? "utimes was not declared in this scope" I'm running xcode 3.0 on a mac 10.5.2 anyone have any suggestions?Thx
#20
With a clean download, following the steps that Martin posted back in November, I got from the pesky utimes error to a working executable.
www.garagegames.com/blogs/87004/14127
Hope that helps,
Jonathan
06/26/2008 (10:22 am)
I had the same thing when I first tried to run Torque on 10.5. My problem was that I had set the SDK to be 10.5, and I shouldn't have done.With a clean download, following the steps that Martin posted back in November, I got from the pesky utimes error to a working executable.
www.garagegames.com/blogs/87004/14127
Hope that helps,
Jonathan
Torque Owner Martin Schultz