Problem Using Torque as a Static Library

#1 In main.cc, you'll see a static bool initLibraries() function. You'll have to make sure to call it or something like it from your Qt main().

#2 Just keep in mind that Torque is in no way designed or written to be used in this manner, so any issues or results you may (or may not) have are areas that most will not have explored...

#3 Tony,
game\main.cc initLibraries() is called. Nothing this far into the startup is amiss. Thanks.

Sephen,
Yep - trust me to strap a rocket to my backside everytime. It's this or build our own monster from the ground up with the OGRE lib. However, I like TGE and its got a huge amount of really good stuff in it. I'll keep pounding for awhile to see if I can get this puppy to bark. Thanks.

Tim

#4 Oh well... was a suggestion.

Something else to try is to look at your Torque Library project in the Project Properties / C++ / Code Generation and make sure the runtime library is exactly the same as that of your QT project.

#5 All,
I have TGE working (more or less) inside Qt. By working I mean that the application comes up with the Qt window and TGE window (later I'll get the TGE rendering inside a Qt window) and the starter.fps to run. To solve the linking issues mentioned in prior posts I modified the IMPLEMENT_CO... macros as follows:

#define IMPLEMENT_CONOBJECT(className) \
bool Init##className = false; \
....
#define IMPLEMENT_CO_NETOBJECT_V1(className) \
bool Init##className = false; \
....
#define IMPLEMENT_CO_DATABLOCK_V1(className) \
bool Init##className = false; \
....
This means every console class file now has a variable like:
bool InitClassName = false;

In addition, I modified the winWindow.cc file run() function as follows:

extern bool LinkConsoleFunctions;
extern bool InitAudioProfile;
extern bool InitGuiFrameSetCtrl;
extern bool InitGuiControlListPopUp;
extern bool InitGuiConsoleEditCtrl;
extern bool InitGuiGraphCtrl;
extern bool InitGameTSCtrl;
extern bool InitGuiBitmapBorderCtrl;
extern bool InitGuiShapeNameHud;
extern bool InitGuiHealthBarHud;
extern bool InitGuiCrossHairHud;
extern bool InitGuiMessageVectorCtrl;
extern bool InitGuiChunkedBitmapCtrl;
extern bool InitGuiInputCtrl;
extern bool InitGuiFadeinBitmapCtrl;
extern bool InitScriptObject;
extern bool InitCameraData;
extern bool InitMissionMarker;
extern bool InitItemData;
extern bool InitSplashData;
extern bool InitProjectileData;
extern bool InitTSShapeConstructor;

extern bool InitPlayerData;
extern bool InitParticleEmitterNodeData;
extern bool InitMissionArea;
extern bool InitSky;
extern bool InitSun;
extern bool InitfxSunLight;
extern bool InitTSStatic;
extern bool InitAIPlayer;

S32 run(S32 argc, const char **argv)
{
// Hacks to ensure consolefunctions and console objects get linked in
LinkConsoleFunctions=true;
InitAudioProfile=true;
InitGuiFrameSetCtrl=true;
InitGuiControlListPopUp=true;
InitGuiConsoleEditCtrl=true;
InitGuiGraphCtrl=true;
InitGameTSCtrl=true;
InitGuiBitmapBorderCtrl=true;
InitGuiShapeNameHud=true;
InitGuiHealthBarHud=true;
InitGuiCrossHairHud=true;
InitGuiMessageVectorCtrl=true;
InitGuiChunkedBitmapCtrl=true;
InitGuiInputCtrl=true;
InitGuiFadeinBitmapCtrl=true;
InitScriptObject=true;
InitCameraData=true;
InitMissionMarker=true;
InitItemData=true;
InitSplashData=true;
InitProjectileData=true;
InitTSShapeConstructor=true;
InitPlayerData=true;
InitParticleEmitterNodeData=true;
InitMissionArea=true;
InitSky=true;
InitSun=true;
InitfxSunLight=true;
InitTSStatic=true;
InitAIPlayer=true;

createFontInit();
windowSize.set(0,0);

S32 ret = Game->main(argc, argv);
createFontShutdown();
return ret;
}

This gets all of the classes I need to get starter.fps to run. Clearly, there are more classes that should be referenced but that will be the next step. This is clearly an ugly hack; redemmed only by the fact that it works. If anyone comes up with a better technique please let me know.

Cheers,
Tim

#6 Clever hack. Congratulations on sucking it up and solving the problem - most people just whine about it and move on. ;)