Use of "Torque Lib"
by Markus Nuebel · in Torque Game Engine · 12/13/2003 (4:59 am) · 6 replies
Hi all.
While staring with Torque, I have checked out the different c++ projects that are building the SDK.
It seems to me that the project "Torque Demo" and "Torque Lib" contain the same files.
While "Torque Demo" compiles to an application, "Torque Lib" compiles to a static library.
With such a setup I have expected the engine to be coded inside the library (Torque Lib) and have an application executable build upon this library, whithout using the sources of the library.
Is there a reason, while the "Torque Demo" application does not use the engine as a lib, but instead is compiled from all the engine sources?
Or has the "Torque Lib" project been added only for convenience?
Best regards
-- Markus
While staring with Torque, I have checked out the different c++ projects that are building the SDK.
It seems to me that the project "Torque Demo" and "Torque Lib" contain the same files.
While "Torque Demo" compiles to an application, "Torque Lib" compiles to a static library.
With such a setup I have expected the engine to be coded inside the library (Torque Lib) and have an application executable build upon this library, whithout using the sources of the library.
Is there a reason, while the "Torque Demo" application does not use the engine as a lib, but instead is compiled from all the engine sources?
Or has the "Torque Lib" project been added only for convenience?
Best regards
-- Markus
About the author
#3
Is there any reason why one wouldn't just want to link the Torque Lib into the main application project?
- Jaba
09/19/2005 (7:58 pm)
This doesn't really answer the initial question, IMHO. It kinda sucks to have to build the same (large) set of files twice, when doing a full build. :)Is there any reason why one wouldn't just want to link the Torque Lib into the main application project?
- Jaba
#4
09/19/2005 (9:48 pm)
Because the Torque Lib is a subset of the full Torque engine... it is only the parts needed by the tools to compile
#5
Couldn't the engine use that lib as well? I'd think it would be cleaner that way.
09/20/2005 (10:39 am)
@Labrat: I see what Jaba is getting at. If those functions are a true subset, then all the stuff in the Torque Lib should also be present in the main engine. So "why compile them twice?"Couldn't the engine use that lib as well? I'd think it would be cleaner that way.
#6
Someday we might change this but for now it works. :)
09/21/2005 (4:50 am)
The lib tends to break things like the console initialization code. So we have the lib and the executable.Someday we might change this but for now it works. :)
Associate Ron Yacketta
EDIT:
compile is the wrong term ;) should be used to link the tools in the torque/tools directory *sigh*