C++ compile succeeds in editor, fails in visual studio

The compile option in the Rocket editor works, but of course, this is only good for hot/temporary builds.

If I try to compile in visual studio, something always fails to compile.

Keep getting two errors messages in particular:

warning MSB8005: The property ‘NMakeBuildCommandLine’ doesn’t exist.

Parameter “basePath” cannot be a relative path.

The UDN page on how to compile mentions the build being Win64 only, yet one of the builds only has a Win32 option.

I installed Visual Studio 2012 Express and patched it with Update3.

I have followed verious setup instructions and suggestions from the forum and UDN.

I have run the GenerateProjectFiles.bat and reinstalled VS 2012 express and its update.

I have tried this with the ShooterGame example and auto generated TPP game.

VS2010 is installed for some other work. In an effort to make sure that is not interfering, I am currently using the uninstall utilities provided by MS to completely remove all VS2012, VS2010 and dotNet related files.

I have never been good with visual studio, nor do I like using. The vast majority of my coding is done using Notepad++ and batch file shortcuts. Visual studio is relegated to the role of a compiler and occaisional debugging.

If anyone has any suggestions on what I am doing wrong, has any more suggestions or an outright solution, please let me know.

Are you building the MyGameEditor target under the “Build and Run” folder? Verify that your configuration is set to Win64 Development (or Debug), right click it and select Build.

Also, which version of Rocket are you using? The most recent release (Beta3, CL#1711197 or the hotfix Beta3v2 CL#1761932) no longer requires GenerateProjectFiles.bat. You should be able to right click the .uproject file and select “Generate Visual Studio Files”. If you installed do a different location than the last beta, there is a change that the batch file is pointing to the wrong build.

My apologies for the delay in answering.

Yes, that worked.
It was just me having a brain fart I guess, trying to compile the wrong thing or some such. I have since created a batch file to do the compiling for me, relegating VS to its debug duties.

I am now a happy chappy :slight_smile: