gavinpugh / vs-android

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

-save-temps compiler switch doesn't work #47

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Right-click on any cpp file in Solution Explorer and select Properties
2. In 'Command Line' section write -save-temps into the 'Additional Options' 
field
3. Try to compile the file.

What is the expected output? What do you see instead?
It should compile.

Visual Studio reports:
as.exe: unrecognized option `--save-temps'
C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Android\Microsoft.Cpp.Android.Targets
(52,5): error MSB6006: "arm-linux-androideabi-g++.exe" exited with code 1.

Build FAILED.

What version of the product are you using? On what operating system?
VS2010 Ultimate SP1, vs-android 0.93, Windows 7 Ultimate SP1

Original issue reported on code.google.com by tbyte...@gmail.com on 15 Nov 2011 at 5:17

GoogleCodeExporter commented 9 years ago
I tried this and got the same error. It looks like it's on the command line 
fine (turn on 'echo command line' to confirm that yourself).

All I can ascertain is that the gcc Google are shipping doesn't support that 
flag. I've used many other flags in the additional options field without issue.

So I'll close this, since it's not an issue with vs-android. Reply though if 
you still think it's valid. I've never used that particular switch before, so 
possibly it does something out of the ordinary.

Original comment by gavin.dj.pugh on 17 Nov 2011 at 4:11

GoogleCodeExporter commented 9 years ago
Well, you're right. Sorry to bother you. It worked earlier in version 0.92, but 
I forgot that I had updated to Android NDK R7 as well, not only to the latest 
vs-android. It seems this switch is not supported in this version of Android 
NDK.

Original comment by tbyte...@gmail.com on 17 Nov 2011 at 9:52

GoogleCodeExporter commented 9 years ago
No worries, man! It's a shame they don't document changes to the gcc they're 
using, in their NDK 'release notes'. Looks like there's nothing about it in 
there.

Original comment by gavin.dj.pugh on 18 Nov 2011 at 10:32