0 error, 2 warnings, can't find my output files
by Warp Zone · in Technical Issues · 12/03/2007 (2:34 pm) · 3 replies
I am using:
TGEA 1.0.3
Microsoft Windows XP Media Center Edition 2005, English for Inspiron XPS 1
Microsoft Visual C++ 2005 v 2.0.50727
DirectX SDK November 2007
Several warning PRJ0041's appeared during first compile, claiming that the project was out of date because it lacked the following files:
'winwlm.h', 'macwin32.h' (repeated several times ) , 'rpcerr.h' , 'rpcmac.h' , 'macname1.h' , 'macpub.h' , 'macapi.h' , and 'macname2.h'
I'm no expect, but I'm guessing these missing files are just some vestegial attempt at mac support.
The following two warnings, however, were noteworthy enough to make it into the final "warnings" tally:
c:\torque\engine\platformwin32\dxversionchecker.cpp(149) : warning C4996: '_wsplitpath' was declared deprecated
c:\program files\microsoft visual studio 8\vc\include\stdlib.h(782) : see declaration of '_wsplitpath'
Message: 'This function or variable may be unsafe. Consider using _wsplitpath_s instead. To disable deprecation, use _CRT_SECURE_NO_DEPRECATE. See online help for details.'
c:\torque\vc8\cmdscan.l(216) : warning C4996: '_vsnprintf' was declared deprecated
c:\program files\microsoft visual studio 8\vc\include\stdio.h(339) : see declaration of '_vsnprintf'
Message: 'This function or variable may be unsafe. Consider using _vsnprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_DEPRECATE. See online help for details.'
I did a little googling, and I guess Microsoft replaced '_vsnprintf' and '_wsplitpath' with some other keywords? I'm not advanced enough to go poking through the code replacing all the variable names. Someone's post suggested turning off depreciation-checking, but I couldn't work out how to do that.
Notes:
- The compile tutorial I'm trying to follow is the one that shipped with TGEA 1.0.3. ( http://tdn.garagegames.com/wiki/TSE/Setup#Note_about_using_Visual_Studio_8_.282005.29_Express_Edition_-_as_at_1.2F5.2F06 )
- I was not given an option to install DirectX in "Debug Mode," and I can't figure out how to launch a "DirectX Properties dialog" from my Windows Control Panel.
- The instructions warn to use a specific older version of DXsdk if using Visual C++ 6.0. Since I am using 2008, I assume (hope) that I can just use the current version of DXsdk. If this is wrong, tell me which version I should be using.
- I started to follow the steps listed under "Note about using Visual Studio 8 (2005) Express Edition - as at 1/5/06" in the tutorial, until I noticed that these Executable, Include, and Library files were already on the list. Is the tutorial out of date or are its instructions incomplete?
Misc Questions:
Where should I expect my binaries to appear, upon a successful compile? I just want to make sure it didn't build and I missed it.
Full output log availible upon request. (I didn't want to clutter this first post with it until I learn more about whatever quote or code tags this forum uses.) I included the 2 warnings I get.
Thanks in advance for any helpful replies.
TGEA 1.0.3
Microsoft Windows XP Media Center Edition 2005, English for Inspiron XPS 1
Microsoft Visual C++ 2005 v 2.0.50727
DirectX SDK November 2007
Several warning PRJ0041's appeared during first compile, claiming that the project was out of date because it lacked the following files:
'winwlm.h', 'macwin32.h' (repeated several times ) , 'rpcerr.h' , 'rpcmac.h' , 'macname1.h' , 'macpub.h' , 'macapi.h' , and 'macname2.h'
I'm no expect, but I'm guessing these missing files are just some vestegial attempt at mac support.
The following two warnings, however, were noteworthy enough to make it into the final "warnings" tally:
c:\torque\engine\platformwin32\dxversionchecker.cpp(149) : warning C4996: '_wsplitpath' was declared deprecated
c:\program files\microsoft visual studio 8\vc\include\stdlib.h(782) : see declaration of '_wsplitpath'
Message: 'This function or variable may be unsafe. Consider using _wsplitpath_s instead. To disable deprecation, use _CRT_SECURE_NO_DEPRECATE. See online help for details.'
c:\torque\vc8\cmdscan.l(216) : warning C4996: '_vsnprintf' was declared deprecated
c:\program files\microsoft visual studio 8\vc\include\stdio.h(339) : see declaration of '_vsnprintf'
Message: 'This function or variable may be unsafe. Consider using _vsnprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_DEPRECATE. See online help for details.'
I did a little googling, and I guess Microsoft replaced '_vsnprintf' and '_wsplitpath' with some other keywords? I'm not advanced enough to go poking through the code replacing all the variable names. Someone's post suggested turning off depreciation-checking, but I couldn't work out how to do that.
Notes:
- The compile tutorial I'm trying to follow is the one that shipped with TGEA 1.0.3. ( http://tdn.garagegames.com/wiki/TSE/Setup#Note_about_using_Visual_Studio_8_.282005.29_Express_Edition_-_as_at_1.2F5.2F06 )
- I was not given an option to install DirectX in "Debug Mode," and I can't figure out how to launch a "DirectX Properties dialog" from my Windows Control Panel.
- The instructions warn to use a specific older version of DXsdk if using Visual C++ 6.0. Since I am using 2008, I assume (hope) that I can just use the current version of DXsdk. If this is wrong, tell me which version I should be using.
- I started to follow the steps listed under "Note about using Visual Studio 8 (2005) Express Edition - as at 1/5/06" in the tutorial, until I noticed that these Executable, Include, and Library files were already on the list. Is the tutorial out of date or are its instructions incomplete?
Misc Questions:
Where should I expect my binaries to appear, upon a successful compile? I just want to make sure it didn't build and I missed it.
Full output log availible upon request. (I didn't want to clutter this first post with it until I learn more about whatever quote or code tags this forum uses.) I included the 2 warnings I get.
Thanks in advance for any helpful replies.
#2
Turns out it's actually/example/TGEA_DEBUG.exe , not /example/demo/torqueDemo.exe I guess we're using different versions.
There is also a TGEA.exe there, but it was created on August 31st. Thanks for the tip, now I know for sure where to check in future. :)
The one thing that bugs me is, why doesn't the compile process inform you that it's writing a file, and announce the full path to the exe? Other compilers I've played with in the past always finished up with a nice obvious output line.
12/03/2007 (3:25 pm)
Found it. :)Turns out it's actually
There is also a TGEA.exe there, but it was created on August 31st. Thanks for the tip, now I know for sure where to check in future. :)
The one thing that bugs me is, why doesn't the compile process inform you that it's writing a file, and announce the full path to the exe? Other compilers I've played with in the past always finished up with a nice obvious output line.
#3
I had the VS 2005 Express for a while, and I remember for sure it was unable to edit resource files, but I think it has the same general IDE elements. You shoudl have a link message, but I don't think it has the filename in it.
Look in your project properties (rt-click on the name in the left panel, select properties) and under linker should be an item "output" which has the path+name to send the final output to. It is, of course, editable to anything you want.
<* Wes *>
12/03/2007 (4:07 pm)
Yes, you are right about the name, I have changed my configuration from Debug.I had the VS 2005 Express for a while, and I remember for sure it was unable to edit resource files, but I think it has the same general IDE elements. You shoudl have a link message, but I don't think it has the filename in it.
Look in your project properties (rt-click on the name in the left panel, select properties) and under linker should be an item "output" which has the path+name to send the final output to. It is, of course, editable to anything you want.
<* Wes *>
Torque Owner Wesley Howe
I found that _CRT_SECURE_NO_DEPRECATE was already defined in my project, just put that in the preprocessor section of your project C++ properties and it should be fine.
If it bothers you, you can use the VS editor to find and replace all the function names later.
<* Wes *>