Topic: Compiling Maratis on Visual Studio/C++ 2010
I've been arguing with getting Maratis to build with Visual Studio/C++ 2010. On my work PC (during lunch, of course) it will build using scons VC's 'cl'. At home I only have Visual C++ 2010 Express which doesn't seem to like running cl from the command line.
There appear to be 2 problems with whatever VC2010 does. The first thing is, the post build step for the project Maratis seems to be failing. I assume this would be that one of the steps is failing, possibly due to the file already being there and prompting to overwrite. I haven't really looked into this properly, I copied the files manually and removed the post build step.
The second thing is that VC2010 defaults to using $(TARGET) for debugging whatever you've compiled, whereas the linker saves to build\$(ProjectName)Debug.exe. I assume in previous versions $(TARGET) got updated to whatever the linker spits out. I have tried changing the Output Directory and Target Name options, which gets the debugger to start running the executable, but the actual executable doesn't seem to have been built properly.
Annoyingly, Visual Studio also doesn't seem to save the Debugger properties which is frustrating.
EDITI've been arguing with getting Maratis to build with Visual Studio/C++ 2010. On my work PC (during lunch, of course) it will build using scons VC's 'cl'. At home I only have Visual C++ 2010 Express which doesn't seem to like running cl from the command line.
There appear to be 2 problems with whatever VC2010 does. The first thing is, the post build step for the project Maratis seems to be failing. I assume this would be that one of the steps is failing, possibly due to the file already being there and prompting to overwrite. I haven't really looked into this properly, I copied the files manually and removed the post build step.
The second thing is that VC2010 defaults to using $(TARGET) for debugging whatever you've compiled, whereas the linker saves to build\$(ProjectName)Debug.exe. I assume in previous versions $(TARGET) got updated to whatever the linker spits out. I have tried changing the Output Directory and Target Name options, which gets the debugger to start running the executable, but the actual executable doesn't seem to have been built properly.
Annoyingly, Visual Studio also doesn't seem to save the Debugger properties which is frustrating.
EDIT: If I can get VC2010 to build and debug nicely, I will share my solution. At the moment, most of the changes have to be done every time
Last edited by Nistur (2012-01-10 11:10:52)