Before I start...
by Wysardry · in Torque Game Engine · 03/27/2004 (3:49 pm) · 10 replies
I've just downloaded Release_1_2_0 via CVS and have a few questions to ask before I attempt to compile everything:-
Should I have downloaded Release_1_2_1 instead?
Which compiler package would be the best to use out of LCC-Win32 (LCC), Dev-C++ (Mingw/GCC), [url=]http://www.smorgasbordet.com/pellesc/]Pelles C[/url] (LCC) or Metrowerks CodeWarrior 5?
I do not currently have a compiler installed on the machine I will be using for Torque, but have used LCC-Win32 and Dev-C++ on my laptop. The Torque documentation only mentions Microsoft Visual C++ 6.0 and Metrowerks Codewarrior 6.0, and there are only setup instructions for the former.
Do I need to download the OpenAL SDK, or will my existing sound drivers be enough? I have nVidia SoundStorm/nForce2 400 integrated sound, which is supposed to already have OpenAL support.
I'm sorry to be asking so many questions, but the machine I will be using doesn't have Internet access, so I'll need to collect all necessary software together first and put it on a CDR.
Should I have downloaded Release_1_2_1 instead?
Which compiler package would be the best to use out of LCC-Win32 (LCC), Dev-C++ (Mingw/GCC), [url=]http://www.smorgasbordet.com/pellesc/]Pelles C[/url] (LCC) or Metrowerks CodeWarrior 5?
I do not currently have a compiler installed on the machine I will be using for Torque, but have used LCC-Win32 and Dev-C++ on my laptop. The Torque documentation only mentions Microsoft Visual C++ 6.0 and Metrowerks Codewarrior 6.0, and there are only setup instructions for the former.
Do I need to download the OpenAL SDK, or will my existing sound drivers be enough? I have nVidia SoundStorm/nForce2 400 integrated sound, which is supposed to already have OpenAL support.
I'm sorry to be asking so many questions, but the machine I will be using doesn't have Internet access, so I'll need to collect all necessary software together first and put it on a CDR.
About the author
#2
03/27/2004 (4:23 pm)
Which documentation? I couldn't find the answers at http://www.garagegames.com/docs/torque.sdk/
#3
I'm sure i've seen build docs for MingW on this site somewhere before, but I just had a look and I can't find them anywhere now. Try searching the forums and resources, etc for mingw.
A lot of the linux build instructions will apply to MingW too so it's worth giving them a read.
However, if you are using a gcc based compiler, and you have some experience with Makefiles, it's pretty easy to figure it out. cd to the Torque dir (where you find the first Makefile), type make and it will pretty much tell you what to do. Where you have to specify an OS, use win32. Binaries end up in the example directory.
Hope that points you in the right direction :)
Tom.
03/27/2004 (5:35 pm)
You could try this: www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=4948I'm sure i've seen build docs for MingW on this site somewhere before, but I just had a look and I can't find them anywhere now. Try searching the forums and resources, etc for mingw.
A lot of the linux build instructions will apply to MingW too so it's worth giving them a read.
However, if you are using a gcc based compiler, and you have some experience with Makefiles, it's pretty easy to figure it out. cd to the Torque dir (where you find the first Makefile), type make and it will pretty much tell you what to do. Where you have to specify an OS, use win32. Binaries end up in the example directory.
Hope that points you in the right direction :)
Tom.
#4
If the Makefile provides obvious options, I should be okay. I'm assuming the problems with the Dev-C++ IDE do not affect the underlying GCC compiler when used from the command line.
I guess I should download Mingw and MSYS separately to be on the safe side.
Thanks.
03/27/2004 (6:32 pm)
Yes, I have used the command line make command with LCC before - to build GLFW, an OpenGL library - but that came with a readme file explaining the switches to use for each compiler and O/S.If the Makefile provides obvious options, I should be okay. I'm assuming the problems with the Dev-C++ IDE do not affect the underlying GCC compiler when used from the command line.
I guess I should download Mingw and MSYS separately to be on the safe side.
Thanks.
#5
Want details about really how big the source code base is search the forums for "torque metrics" I post metrics every once in a while when major releases are done.
All the documentation is available if you just click on the purchased products link.
03/27/2004 (8:15 pm)
Yes DevC++ itself just can't handle the crazy number of files that make up Torque it just crashes while tyring to import the visual studio workspace file, and adding building the project from scratch would probably fail also, but I didn't try it was less effort to just upgrade my Visual Studio. Want details about really how big the source code base is search the forums for "torque metrics" I post metrics every once in a while when major releases are done.
All the documentation is available if you just click on the purchased products link.
#6
I've downloaded them all anyway to be on the safe side, but I don't relish the prospect of sorting through them all if an essential file is missing from the main Mingw archive.
I'm not sure how many of the Torque files are used when compiling on Windows, but apparently I have 4735 files in 451 directories, which takes up approximately 110Mb space.
The most recent metrics post I could find was from mid-December, and says there should be 1579 source files.
I've looked through the relevant sections of the "Getting Started" guide and the main documentation, but ended up browsing the forums to find out about compilers other than Visual C++
If I do manage to compile everything successfully using Dev-C++ from the command line (once I've had some sleep) I'll let everyone know here.
03/27/2004 (10:45 pm)
I certainly hope that the version of Mingw included with Dev-C++ will do the job, as there it's not immediately obvious to me which files I need from the Mingw site, and the main download alone is bigger than the Dev-C++ package.I've downloaded them all anyway to be on the safe side, but I don't relish the prospect of sorting through them all if an essential file is missing from the main Mingw archive.
I'm not sure how many of the Torque files are used when compiling on Windows, but apparently I have 4735 files in 451 directories, which takes up approximately 110Mb space.
The most recent metrics post I could find was from mid-December, and says there should be 1579 source files.
I've looked through the relevant sections of the "Getting Started" guide and the main documentation, but ended up browsing the forums to find out about compilers other than Visual C++
If I do manage to compile everything successfully using Dev-C++ from the command line (once I've had some sleep) I'll let everyone know here.
#7
Re: metrics. I keep a clean copy of TGE head laying around that I update every now and then. It hasnt been updated in a few weeks, but that's 103MB and contains 4478 files and 443 folders. Probably the reason for the vast difference in what you found in the forums and what you're downloading is the metrics are limited to the engine source code (or possibly the tools too, not sure, havent checked), and thus wont include the scripts, assets, etc from the Torque Demo.
T.
03/27/2004 (11:45 pm)
Re: Dev-C++. As long as you have all the right libs and headers, I dont see why using the gcc from Dev-C++ won't work. It sounds like it's issues are limited to the IDE, but you never know. Re: metrics. I keep a clean copy of TGE head laying around that I update every now and then. It hasnt been updated in a few weeks, but that's 103MB and contains 4478 files and 443 folders. Probably the reason for the vast difference in what you found in the forums and what you're downloading is the metrics are limited to the engine source code (or possibly the tools too, not sure, havent checked), and thus wont include the scripts, assets, etc from the Torque Demo.
T.
#8
I have heard the that the Elcipse IDE will but, as of yet I have not been able to get it to work (though some here have).
You may be best getting yourself a copy of MS V C 6.0 (also check your OS for campatibility).. It's one of the tools that most of the examples are built around.
03/28/2004 (9:53 pm)
From what I understand the compiler aspect will work minGW, but the IDE of DevCpp can not handel it at this time.I have heard the that the Elcipse IDE will but, as of yet I have not been able to get it to work (though some here have).
You may be best getting yourself a copy of MS V C 6.0 (also check your OS for campatibility).. It's one of the tools that most of the examples are built around.
#9
Did you try the resource I posted the URL for earlier in this thread? That was the Eclipse resource that Ron did.
I use Visual C++ on Windows so I havent tried it, but last I heard that resource worked fine and the recentish comments in the resource look promising.
T.
03/29/2004 (3:56 am)
@Donny,Did you try the resource I posted the URL for earlier in this thread? That was the Eclipse resource that Ron did.
I use Visual C++ on Windows so I havent tried it, but last I heard that resource worked fine and the recentish comments in the resource look promising.
T.
#10
I uninstalled Dev-C++ and installed the latest stable versions of MinGW and MSYS, added "C:\MinGW" to the path in autoexec.bat opened the fstab.example file and changed the example paths to:-
c:/MinGW /mingw
c:/torque /torque
Then saved the file as "fstab". After rebooting, I ran MYSYS and typed:-
cd /torque
make -f mk/configure.mk OS=WIN32 COMPILER=GCC3 BUILD=DEBUG
make
There were a string of warnings, but the Linux GCC docs say to ignore them, so I did.
But (you knew one was coming, didn't you?), although the torqueDemo_DEBUG.exe runs, there are several missing image errors in the log file.
Is this normal?
This is Release_1_2_0 btw.
03/30/2004 (12:18 am)
When I tried using the GCC included with Dev-C++ I had about a dozen error messages along the lines of "file cannot be created", although this was probably some sort of path issue.I uninstalled Dev-C++ and installed the latest stable versions of MinGW and MSYS, added "C:\MinGW" to the path in autoexec.bat opened the fstab.example file and changed the example paths to:-
c:/MinGW /mingw
c:/torque /torque
Then saved the file as "fstab". After rebooting, I ran MYSYS and typed:-
cd /torque
make -f mk/configure.mk OS=WIN32 COMPILER=GCC3 BUILD=DEBUG
make
There were a string of warnings, but the Linux GCC docs say to ignore them, so I did.
But (you knew one was coming, didn't you?), although the torqueDemo_DEBUG.exe runs, there are several missing image errors in the log file.
Is this normal?
This is Release_1_2_0 btw.
Torque Owner Jarrod Roberson