Anyone use VS 2008 beta to compile and get it to work?
by Rick Kelley · in Torque Game Engine · 11/13/2007 (11:46 am) · 5 replies
I tried the VS 2008 beta 2 and allowed it to convert, but no dice yet. A lot of the errors start out with:
Error 1 error C2440: 'initializing' : cannot convert from 'const wchar_t [22]' to 'const UTF16 *' c:\torque\sdk\engine\platformwin32\winwindow.cc 34 Torque Demo
which of course defined as:
typedef unsigned short UTF16; ///< Compiler independent 16 bit Unicode encoded character
or this error:
Error 14 error C2664: 'CreateProcessW' : cannot convert parameter 2 from 'UTF16 [1024]' to 'LPWSTR' c:\torque\sdk\engine\platformwin32\winwindow.cc 1612 Torque Demo
which is pointing to:
CreateProcess( NULL,
#ifdef UNICODE
b,
#else
buf,
#endif
NULL,
NULL,
false,
CREATE_NEW_CONSOLE | CREATE_NEW_PROCESS_GROUP,
NULL,
NULL,
&si,
&pi );
return( true );
}
Error 1 error C2440: 'initializing' : cannot convert from 'const wchar_t [22]' to 'const UTF16 *' c:\torque\sdk\engine\platformwin32\winwindow.cc 34 Torque Demo
which of course defined as:
typedef unsigned short UTF16; ///< Compiler independent 16 bit Unicode encoded character
or this error:
Error 14 error C2664: 'CreateProcessW' : cannot convert parameter 2 from 'UTF16 [1024]' to 'LPWSTR' c:\torque\sdk\engine\platformwin32\winwindow.cc 1612 Torque Demo
which is pointing to:
CreateProcess( NULL,
#ifdef UNICODE
b,
#else
buf,
#endif
NULL,
NULL,
false,
CREATE_NEW_CONSOLE | CREATE_NEW_PROCESS_GROUP,
NULL,
NULL,
&si,
&pi );
return( true );
}
#2
11/19/2007 (1:36 pm)
I allowed it to convert the V7 project. Didn't try the vs2005 one 
#3
11/19/2007 (2:20 pm)
That's probably the problem there, because like Johnathon, I was able to convert the VS 2005 solutions and compile without errors (lots of warnings, but that's in VS 2005 as well, mostly sprintf and such).
#4
When converting to a new version of Visual Studio, always convert the project available for the most recent previous version of VS, regardless of whether or not that was the one you were using before. Sometimes that will mean you have to add/remove files from the converted project if it wasn't the one you were using before, but that is far easier than tracking down subtle differences in compiler settings.
T.
11/19/2007 (3:32 pm)
The errors you are seeing will also occur in VS2005. The VS2005 project is setup correctly to fix those problems, so as mentioned above it should convert cleanly barring any additional nuances of VS2008.When converting to a new version of Visual Studio, always convert the project available for the most recent previous version of VS, regardless of whether or not that was the one you were using before. Sometimes that will mean you have to add/remove files from the converted project if it wasn't the one you were using before, but that is far easier than tracking down subtle differences in compiler settings.
T.
#5
Without changes, Torque is likely highly dependent on "virtualization" on Vista. Torque likes to write output files such as the user preferences to the installed directory rather than the suggested "User" settings folders. If the install folder is in the default: c:\program file (or similar) heirarchy that is protected in Vista, virtualization creates automatic translations that let the program open files for writing elsewhere.
---
I looked around and didn't immediately find a way to enable virtualization. If anyone looks into this and has more knowledge, please speak up.
11/22/2007 (7:27 am)
Be careful to check warnings during conversion. With the reelased version, I received the following for the TorqueDemo project: Quote:
This application has been updated to include settings related to the User Account Control (UAC) feature of Windows Vista. By default, when run on Windows Vista with UAC enabled, this application is marked to run with the same privileges as the process that launched it. This marking also disables the application from running with virtualization. You can change UAC related settings from the Property Pages of the project.
Without changes, Torque is likely highly dependent on "virtualization" on Vista. Torque likes to write output files such as the user preferences to the installed directory rather than the suggested "User" settings folders. If the install folder is in the default: c:\program file (or similar) heirarchy that is protected in Vista, virtualization creates automatic translations that let the program open files for writing elsewhere.
---
I looked around and didn't immediately find a way to enable virtualization. If anyone looks into this and has more knowledge, please speak up.
Torque Owner Johnathon