Suggestion: Use PHYSXSDK environment variable
by Andreas Johansen · in Torque 3D Professional · 05/09/2009 (4:46 pm) · 7 replies
Instead of using an absolute path for the PhysX SDK in the projects (include paths, file paths), use the PHYSXSDK environment variable. Example for an include path would then be $(PHYSXSDK)\NxCharacter\include
Unless you install the PhysX SDK to the default path and isn't running WIN64 (default path is then under "Program Files (x86)") and not a localized version of windows either (would be under "Programfiler" on a Norwegian version) then you will be unable to compile the PhysX demo project from the get go.
Only thing is I don't actually think PhysX SDK defines that environment variable, but it's become a sort of standard when working with PhysX.
Unless you install the PhysX SDK to the default path and isn't running WIN64 (default path is then under "Program Files (x86)") and not a localized version of windows either (would be under "Programfiler" on a Norwegian version) then you will be unable to compile the PhysX demo project from the get go.
Only thing is I don't actually think PhysX SDK defines that environment variable, but it's become a sort of standard when working with PhysX.
#2
05/10/2009 (5:18 am)
Shouldn't that be TORQUE_PHYSX_PATH from looking at the project.conf for the PhysX demo?$ENV_PATH = getenv( "TORQUE_PHYSX_PATH" );
#3
05/10/2009 (5:22 am)
I'd still suggest not resolving that path when creating the projects as people working on the same project, but with different install paths for PhysX SDK would have to keep re-generating the projects if someone made a change to a project and say committed it to SVN. Just makes it more friendly to work with if the paths are resolved by VS instead of that project generator. 
#4
07/19/2009 (3:45 pm)
OK.. So this variable is set in my system, so why do I have to re-enter all the PhysX info for each Beta? am I missing something here, or do I really need to create a PhysX template then generate a project? 
#5
@Randy - You talking about from Toolbox?
07/23/2009 (2:47 pm)
@Andreas - I would prefer resolving the TORQUE_PHYSX_PATH environment var at compile time, but 1. the current project generator doesn't support that feature and 2. i don't think that works for adding .cpp files.@Randy - You talking about from Toolbox?
#6
Yes.... I wanted to setup a template with PhysX and create new projects on that.
I went back and checked and looks like my original template I created did not build anyway(used from the PhysX demo) so I assume once I get that to build correctly and move over to the template I should be ok....
But it seems if I have the SDK installed and my variables set, I should not have to go into the PhysX demo and add the SDK paths should I?
Randy
07/23/2009 (3:24 pm)
@Tom...Yes.... I wanted to setup a template with PhysX and create new projects on that.
I went back and checked and looks like my original template I created did not build anyway(used from the PhysX demo) so I assume once I get that to build correctly and move over to the template I should be ok....
But it seems if I have the SDK installed and my variables set, I should not have to go into the PhysX demo and add the SDK paths should I?
Randy
#7
04/15/2012 (8:46 pm)
I think the problem was when you installed torque (and the templates) you didn't have your environment variable set so it didn't build the templates. I would just suggest reinstalling 
Associate Tom Spilman
Sickhead Games