search

gavinpugh / vs-android

Integrated development of Android NDK C/C++ software with Microsoft Visual Studio.
Other
119 stars 34 forks source link

vs-android_launch.cmd fails with absolute intermediate output path #110

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
We use a fully pathed intermediate output directory in our projects, so when we 
press F5 in Visual Studio 2012 on Windows 7, we get a "Unable to start program 
'c:\path_to_project\c:\path_to_intermediate_output\vs-android_launch.cmd' The 
filename, directory name, or volume label syntax is incorrect." error because 
the project path has been concatenated with the intermediate path. The problem 
stems from the required vs-android_launch.cmd being created in the intermediate 
output path, based on line 381 of Microsoft.Cpp.Android.targets:

GenerateCmdFilePath            ="$(IntDir)\vs-android_launch.cmd"

But both of the Microsoft.Cpp.Android.props files have the following on line 27:

<RemoteDebuggerCommand>$(ProjectDir)$(IntDir)vs-android_launch.cmd</RemoteDebugg
erCommand>

This means that the .cmd file isn't created in the same place that it is 
created from. The above line needs to be changed to:

<RemoteDebuggerCommand>$(IntDir)\vs-android_launch.cmd</RemoteDebuggerCommand>

I assume this will also work with relative intermediate paths.

Thanks,

Rich

Original issue reported on code.google.com by richjfor...@gmail.com on 23 Dec 2013 at 2:20

GoogleCodeExporter commented 9 years ago

Original comment by gavin.dj.pugh on 3 Jan 2014 at 6:20