TGE Compiler mistakes
by David Dougher · in Torque Game Engine · 10/05/2004 (1:44 pm) · 2 replies
I had an occasion to do a bit of housecleaning this week on my copy of torque and I found a couple of minor errors in the compile under both VC6 and VC7. Here's a brief list
engine\console\objectTypes.h
engine\platformWIN32\platformAL.h
Both these files are referenced in the builds but they have been removed from the engine or moved elsewhere. This is true under both Torque Demo and Torque Library.
Next was a quick comparison of the Torque demo files and the Torque Library. The following files are listed in the Demo but not in the Library. The .h files are probably not necessary but the .cc files should probably be added.
engine\game\fps\guiCrossHairHud.cc
engine\game\fx\fxLight.cc & h
engine\audio\audioStreamSource.h
audioStreamSourceFactory.h
vorbisStream.cc
vorbixStream.h
vorbisStreamSource.cc & h
engine\console\objectTypes.h
engine\platformWIN32\platformAL.h
Both these files are referenced in the builds but they have been removed from the engine or moved elsewhere. This is true under both Torque Demo and Torque Library.
Next was a quick comparison of the Torque demo files and the Torque Library. The following files are listed in the Demo but not in the Library. The .h files are probably not necessary but the .cc files should probably be added.
engine\game\fps\guiCrossHairHud.cc
engine\game\fx\fxLight.cc & h
engine\audio\audioStreamSource.h
audioStreamSourceFactory.h
vorbisStream.cc
vorbixStream.h
vorbisStreamSource.cc & h
About the author
Owner - Pariah Games, Adjunct Professor - Bristol Community College, Mentor - Game Design - Met School Newport, Mentor - Game Design - Met School Providence
#2
If the purpose of the Library is just for the compilation of the tools then either the library needs some real housecleaning or you simply put everything in and let the compiler skip those it doesn't need. I could be entirely off-base here but I should think the tools need considerably fewer files than the library currently carries if tools compilation is its sole function. 80+ gui functions come to mind.
Either way, as it stands now, it seems inconsistent and that is more dangerous than either.
10/05/2004 (3:33 pm)
OK. I could buy the rationale except.... Only these nine files are NOT necessary? All the others in every subdirectory are present in the Library build so we need them all? Including three other Vorbis sources? And fxLight doesn't need to be compiled in for lighting but fxSunlight does? If the purpose of the Library is just for the compilation of the tools then either the library needs some real housecleaning or you simply put everything in and let the compiler skip those it doesn't need. I could be entirely off-base here but I should think the tools need considerably fewer files than the library currently carries if tools compilation is its sole function. 80+ gui functions come to mind.
Either way, as it stands now, it seems inconsistent and that is more dangerous than either.
Associate James Urquhart
The Torque Library project only contains the engine code *required* to build map2dif, texture2bm8, buildWad, and whatever other tools there are.
The engine is in this library so that the tools can link quickly (as opposed to slowly if you kept linking all the engine obj's together aswell as the tool obj's).
Because of this, it is not a good idea to start putting in stuff like the vorbis sources.
The headers are not critical to the project, as all you'll realistically be compiling is the .cc files.
If your wondering why torque itself doesn't just use the library, its mainly due to the fact that linking becomes "bodged", so all the ConsoleObject's, ConsoleFunction's, and so on will fail to register.
On another note, it would potentially give the wrong signal to developers (e.g. it would seem more like an "API" or "toolkit" than a "game engine").