Cautions for MS VS .NET users
by Dreamer · in Torque Game Engine Advanced · 06/07/2004 (8:26 am) · 7 replies
I have spent the last 48 hours trying to get TSE to compile properly.
First point, you cannot just load the VC6 .dsw and have it convert there are somethings you need to do first.
#1 Open one at a time each project in wordpad
#2 Go through each project and do a search and replace $(InputPath) with "$(InputPath)"
#3 After you have done that you may now do a conversion as normal.
#4 Select the TSE project in Solution Explorer then go to Project Properties Window, select Debug and add ..\example as the working directory
Second point, TSE WILL NOT compile without the Microsoft Windows SDK (This is 13 files 25 MB each and you will have to google for it). But even after that is installed you need to locate at a minimum "strsafe.h" and make sure to copy it to vc7\include directory, in wherever it was you decided to install visual studio.
For some reason this file is needed by NV_Error.h
If you do not do the second step you will continously get compile time errors claiming the file cannot be opened, and this will stay this way, no matter how you point Visual Studio to the file, so just remember to make sure that file is in your include directory PRIOR to trying to compile.
Well thats it and I hope this helps people.
First point, you cannot just load the VC6 .dsw and have it convert there are somethings you need to do first.
#1 Open one at a time each project in wordpad
#2 Go through each project and do a search and replace $(InputPath) with "$(InputPath)"
#3 After you have done that you may now do a conversion as normal.
#4 Select the TSE project in Solution Explorer then go to Project Properties Window, select Debug and add ..\example as the working directory
Second point, TSE WILL NOT compile without the Microsoft Windows SDK (This is 13 files 25 MB each and you will have to google for it). But even after that is installed you need to locate at a minimum "strsafe.h" and make sure to copy it to vc7\include directory, in wherever it was you decided to install visual studio.
For some reason this file is needed by NV_Error.h
If you do not do the second step you will continously get compile time errors claiming the file cannot be opened, and this will stay this way, no matter how you point Visual Studio to the file, so just remember to make sure that file is in your include directory PRIOR to trying to compile.
Well thats it and I hope this helps people.
#2
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
It's an interactive Windows Update-style thing.
Choose Core SDK on the left, then Install this SDK on the right.
After it does it's little scanning thing, unselect the docs and samples and the 64-bit environment. This leaves you with a 31MB download.
After it's done (if it doesn't do it automatically), go into VS and add the include and lib dirs to the compiler search path (Options->Directories I think).
This way you have a small download and don't have to copy any headers.
06/07/2004 (10:25 am)
You can download the Platform SDK here:http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
It's an interactive Windows Update-style thing.
Choose Core SDK on the left, then Install this SDK on the right.
After it does it's little scanning thing, unselect the docs and samples and the 64-bit environment. This leaves you with a 31MB download.
After it's done (if it doesn't do it automatically), go into VS and add the include and lib dirs to the compiler search path (Options->Directories I think).
This way you have a small download and don't have to copy any headers.
#3
map2dif warning LNK4089: all references to 'OLEAUT32.dll' discarded by /OPT:REF
map2dif warning LNK4089: all references to 'd3d9.dll' discarded by /OPT:REF
map2dif warning LNK4089: all references to 'ole32.dll' discarded by /OPT:REF
Just curious what may be going on here? Any ideas?
06/07/2004 (10:48 am)
Ok I am getting some very strange warnings now, and can't seem to figure for the life of me what they are complaining about...map2dif warning LNK4089: all references to 'OLEAUT32.dll' discarded by /OPT:REF
map2dif warning LNK4089: all references to 'd3d9.dll' discarded by /OPT:REF
map2dif warning LNK4089: all references to 'ole32.dll' discarded by /OPT:REF
Just curious what may be going on here? Any ideas?
#4
06/07/2004 (10:50 am)
Oh and yes I have VS .NET 2002
#5
06/07/2004 (11:11 am)
Those warnings are harmless. Those libraries are in the link settings, but apparently aren't actually used so the linker isn't linking them in.
#6
I have been working also in VS2002. I already installed the Platform SDK and copied the "strsafe.h" file. That eliminated the compiling errors in the engine.
However, I have been looking all the files under vc6 file folder and I cannot find the $InputPath expression. Is that the exact name I should look for, or the files to be corrected are in some other folder??
06/08/2004 (12:14 pm)
Hello Trudy:I have been working also in VS2002. I already installed the Platform SDK and copied the "strsafe.h" file. That eliminated the compiling errors in the engine.
However, I have been looking all the files under vc6 file folder and I cannot find the $InputPath expression. Is that the exact name I should look for, or the files to be corrected are in some other folder??
#7
Get WinGREP it's free and easy to use.
http://www.wingrep.com/
After you have installed wingrep, point it to your vc6 directory and have it do a regular expression search for $(InputPath)
It will show you what files this is contained in.
Next do a replacement operation telling it "$(InputPath)"
With the quotes
It will then search all files automatically and do the replacement for you.
(Just wish I'ld have known about it sooner)
06/08/2004 (12:45 pm)
I found a much easier way to do this rather than my previous instructions.Get WinGREP it's free and easy to use.
http://www.wingrep.com/
After you have installed wingrep, point it to your vc6 directory and have it do a regular expression search for $(InputPath)
It will show you what files this is contained in.
Next do a replacement operation telling it "$(InputPath)"
With the quotes
It will then search all files automatically and do the replacement for you.
(Just wish I'ld have known about it sooner)
Associate Kyle Carter