vs-android is intended to provide a collection of scripts and utilities to support integrated development of Android NDK C/C++ software under Microsoft Visual Studio.

Currently vs-android only works under Visual Studio 2010. Earlier versions lack the MSBuild integration with the C/C++ compilation systems.

Cygwin is not required at all to use vs-android, thankfully!

At a bare minimum the Android NDK needs to be installed. This will allow compilation of C/C++ code:

• http://developer.android.com/sdk/ndk/index.html

Get the NDK listed under "(32-bit target)". You can use either the "Windows 32-bit" or "Windows 64-bit" version, but make sure the target version is 32-bit.

In order to build an apk package to run on an Android device, you'll also require:

The Android SDK:

• http://developer.android.com/sdk/index.html

The Java JDK:

• http://www.oracle.com/technetwork/java/javase/downloads/index.html

Apache Ant:

• http://ant.apache.org/

Documentation for vs-android can be found here:

• http://code.google.com/p/vs-android/

Installation:

• http://code.google.com/p/vs-android/wiki/Installation

Troubleshooting:

• http://code.google.com/p/vs-android/wiki/Troubleshooting

Next version

Highlights:

• New toolchain: clang-3.4
• New architecture: arm7v-a-hard
• New standard C++ libraries (STL): libc++-shared, libc++-static
• Vastly improved Intellisense support
• Support for Link Library Dependencies of referenced projects
• Referenced projects are added to library dependencies (if Link Library Dependencies is set)

Bug fixes:

• Include directories are now ordered so that the user may override the system headers
• General properties can now be set through user property sheets
• Error message conversion (GNU style to VS style) is no longer sluggish

New options:

• Thumb Mode (ARM only)
• NEON Instrinsics (ARM only)
• C++ Language Standard
• Short wchar_t
• Default Symbol Visibility
• No Executable Stack (and others)

Breaking changes:

• ThumbMode is a general setting now since it affects both compilation (of every compilation unit) and linkage (with either ARM or Thumb variants of the gcc libraries). As such, you should assign it per-project.

Engineering notes:

• In previous versions, the same set of switches was passed to the internal Intellisense compiler and to the toolchain compiler (e.g. gcc). This worked in many cases (in particular thanks to the Intellisense compiler supporting the -I and -D switches in addition to /I and /D), but failed in others (/TC vs. -x c). In this version, Visual Studio sees only the switches that affect Intellisense, while the GccCompile MSBuild task relies on its own set of switches.

As a side effect, you'd no longer see GCC switches in the Properties window. Instead, compiler features that are supported by Intellisense are controlled through CL-like switches (e.g. /TC) and other compiler features were assigned __VA_FEATURE defines which hint about their availability to the "polyfill" header.

To inspect the command line passed to gcc or clang, use the 'Echo Command Line' property. To inspect the command line passed to Intellisense, go to Tools | Options, then select Text Editor | C/C++ | Advanced and set the following Diangostic Logging settings: Enable Logging: True Logging Level: 5 Logging Filter: 8

• "Polyfill" headers (gcc.h, clang.h, intellisense.h) are provided for Intellisense. They make an effort to simulate gcc/clang environment and, at the same time, to reduce the number of errors during Intellisense parsing. You may introduce additional hacks to the intellisense.h header.

• Hint: Whenever the polyfill headers are not enough and you are haunted by Intellisense errors, #ifdef INTELLISENSE can be used to provide an alternative code path for the Intellisense compiler.

v0.963 - 19th July 2014

• Fix for issue with the "Windows 64-bit" NDK ("TRACKER : error TRK0002: Failed to execute command"). Thanks to Ilya Konstantinov for the fix.
• Added warning message for using the new "(64-bit Target)" NDK. ** Confusingly there are 32-bit and 64-bit Windows flavors of the "(32-bit Target)" and "(64-bit Target)" NDKs. ** vs-android only supports the "(32-bit Target)" NDK currently.
• Also tested vs-android against the new r10 NDK. All toolchains and platforms are current.

v0.962 - 9th June 2014

• Added support for lone-installs of Visual Studio 2013. ** Thanks to ted@lindenlab, and "mellean". I simplified the approach in the end, using project imports rather than duplicating code.
• Fixed pre/post-build steps not functioning correctly. ** Thanks to "mellean" for the fix.
• Tested against new "r9d" NDK. Appears to work fine, please let me know on the "Issues" page if I am mistaken.

v0.961 - 24th February 2014

• Added Precompiled Header support. Thanks to help from Richard Forster.
• PCH support works similarly to the Win32/x64 compilers. You can enable "Create" for the compilation unit which should create the PCH, and "Use" for the project so have all files use that PCH.
• Projects mistakenly setting the ObjectFileName to a directory, will now have an explanatory error.
• /libs/armeabi-v7a is now used when the architecture is set to "armeabi-v7a". This addresses an issue when submitting apk's to the Play Store. Thanks to Ilja Plutschouw.
• The default "PlatformToolset" for newly added configurations is now correctly set. Thanks to Chuck Evans.
• The BrowseInformation flag is now ignored for ClCompile. Oft-imported setting when creating an Android platform on a Win32 project. Compilation fails if it was enabled. Thanks to C.Aragones for the headsup.

v0.96 - 4th January 2014

• Visual Studio 2013 has preliminary support now. It requires VS2012 to be installed alongside it. Unfortunately Microsoft have radically changed how MSBuild scripts implement new platforms. VS2012 express is probably fine.
• Fix for running on the r9 NDKs. The minimum requirement is now NDK r9c.
• New NDK sees 4.3.3 and 4.7 GCC toolchains removed, and 4.8 added. vs-android now reflects these changes.
• GCC 4.8 however still seems to have issues when using the STL. It appears fine if you don't use STL. Suggestions welcome on how to address it, my Google-fu has failed me when looking up the link errors. Stick with GCC 4.6 if you need STL support.
• Added support for missing Android API targets: 12, 13, and 15 through 19. Goes up to Android 4.4 API now.

v0.951 - 22nd May 2013

• Fix for running on machines with a lone install of vs2010. I was doing all my testing on machines which have a dual vs2010 and vs2012 install. Apologies.

v0.95 - 22nd May 2013

• Visual Studio 2012 is now fully supported.
• There are separate installers for vs2010 and vs2012. Scripts are identical between version, via use of conditionals in MSBuild. However both use different supporting DLL files.
• .vcxproj and .sln files are cross-compatible between vs2012 and vs2010. Support for vs2010 will continue for vs-android in the foreseeable future.
• The x64 version of the NDK is now supported.
• Fix for Google breaking change to paths: "4.6.x-google" -> "4.6".
• The default GCC toolchain version has been changed from 4.4.3 to 4.6.
• The build scripts are now compliant with NDK r8e. Previous NDK versions are no longer supported.
• GCC 4.7 is now an available toolchain choice. However, it is not currently usable with the STL. Google state that 4.7 is still experimental. I'd welcome any suggested fix, if it does indeed work in ndk-build.

v0.94 - 24th July 2012

• Completely reworked the deploy and run portions of vs-android.
• Deploy has its own configuration pane: "Android Deployment", and saves these settings to the .user file.
• The Deployment process in general is much more robust. "Build->Cancel" also now works correctly when deploying.
• "Build->Deploy Solution/Deploy Project" now works on Android APK projects, to simply run the deploy step. Enable the "Deploy" checkbox for your project in the Solution "Configuration Manager" to enable this.
• You can now run a deployed app by using "Debug->Run" (F5)! It's a bit of a hacky method, but appears to work fine.
• NDK r8b was a breaking change for vs-android. This version now requires r8b or newer to be installed.
• Fixed breaking changes to the location of libstdc++ STL libraries.
• Fix for Google breaking change to x86 paths: "i686-android-linux" -> "i686-linux-android".
• Added support for the new GCC 4.6 toolchains.
• Added support for the new MIPS toolchains.
• Tested and hopefully fixed issues such that vs-android works fully with a 64-bit JDK install.
• Fix to make it possible to build projects in paths that contain spaces. Thanks to 'null77'.
• Added 'Forced Include File' to "C/C++ -> Advanced" property sheet. Thanks to 'danfilner'.
• Fix to make sure ARM5/ARM7 GCC flags are passed correctly to the compiler. Thanks to 'Drew Dunlop'.

v0.93 - 13th November 2011

• NDK r7 was a breaking change for vs-android. This version now requires r7 or newer to be installed.
• Fixed breaking changes to the location of STL libraries. Also fixed new linking issues introduced by STL changes.
• Removed support for defunct arm 4.4.0 toolset.
• Added support for android-14, Android API v4.0.
• Added support for the dynamic (shared) version of the GNU libstdc++ STL.
• Tested against newest JDK - jdk-7u1-windows-i586.
• Added support for building assembly files. '.s' and '.asm' extensions will be treated as assembly code.
• Correct passing of ANT_OPTS to the Ant Build step. Thanks to 'mark.bozeman'.
• Corrected expected apk name for release builds.
• Added to Ant Build property page; the ability to add extra flags to the calls to adb.
• Fixed bug with arm arch preprocessor defines not making it onto the command line.
• Fixed bad quote removal on paths, in the C# code. Thanks to 'hoesing@kleinbottling'.
• Removed stlport project from Google Code - This was an oversight by Google in the r6 NDK, prebuilt is back again.
• Updated sample projects to work with R15 SDK tools.

v0.92 - 3rd August 2011

• Fixed jump-to-line clickable errors. Reworked code to use regular expressions instead. Tried a number of different compiler/linker warnings and errors and all seems to be good
• Default warning level is now 'Normal Warnings', instead of 'Disable All Warnings'. Whoops!
• Fixed rtti-related warnings when compiling .c files with 'Enable All Warnings (-Wall)', turned on.

v0.91 - 2nd August 2011

• Windows debugger is now usable. Fixed 'CLRSupport' error.
• Error checking to ensure the 32-bit JDK is used.
• Added JVM Heap options to Ant Build step. Initial and Maximum sizes are able to be set there now.
• Added asafhel...@gmail's 'clickable errors from compiler' C# code.
• Modified clickable errors code to also work with #include errors, which specify the column number too.
• Added clickable error support to linker too.

v0.9 - 20th July 2011

• Major update, hence the skip in numbers. Closing in on a v1.0 release.
• Verified working with Android NDK r5b, r5c, and r6.
• Much of vs-android functionality moved from MSBuild script to C# tasks. Similar approach now to Microsoft's existing Win32 setup.
• Dependency checking rewritten to use tracking log files.
• Dependency issues fixed, dependency checking also now far quicker.
• Android Property sheets now completely replace the Microsoft ones, no more rafts of unused sheets.
• Property sheets populated with many options. Switches are no longer hard-coded within vs-android script.
• STL support added. Choice between 'None', 'Minimal', 'libstdc++', and 'stlport'.
• Support for x86 compilation with r6 NDK.
• Full support for v7-a arm architecture, as well as the existing v5.
• Support for Android API directories other than just 'android-9'.
• Separated support for 'dynamic libraries' and 'applications'. Applications build to apk files.
• Response files used in build, no more command-line length limitations.
• Deploy and run within Visual Studio, adb is now invoked by vs-android.
• 'Echo command lines' feature fixed.
• All support SDK/libs (NDK, SDK, Ant, JDK) are okay living in directories with spaces in them now.
• All bugs logged within Google Code are addressed.

v0.21 - 10th Feb 2011

• Fixed issues with the 'ant build' step.
• Added a sensible error message if the NDK envvar isn't set, or is set incorrectly.

v0.2 - 1st Feb 2011

• Changed default preprocessor symbols to work the same way Microsoft's stuff does. Should fix any issues with intellisense as well.
• Added support for scanning header dependencies

v0.1 - 30th Jan 2011

• Initial version.
• All major functionality present, barring header dependency checking.

asafhel...@gmail.com - Initial 'clickable errors from compiler' C# code. mark.bozeman - Fix for Ant Build to correctly pass ANT_OPTS. hoesing@kleinbottling - Fix for the bad quote removal on paths, in the C# code. null77 - Fix so that projects can be built in paths that contain spaces. danfilner - Addition of "Forced Include File" to C/C++ property sheet. Drew Dunlop - Fix so that ARM5/ARM7 GCC flags are passed correctly to the compiler. Richard Forster - Assistance with Precompiled Header support. Ilja Plutschouw - /libs/armeabi-v7a/ fix. C.Aragones - Highlighted BrowseInformation issue. ted@lindenlab - VS2013 lone installs. "mellean" - VS2013 lone installs, and pre/post-build step fixes. Ilya Konstantinov - "TRACKER : error TRK0002: Failed to execute command" 64-bit NDK fix.

"Inside the Microsoft Build Engine: Using MSBuild and Team Foundation Build" Authors: Sayed Ibrahim Hashimi, William Bartholomew

"Microsoft C/C++ Visual Studio 2010 Build Implementation" Located here: %ProgramFiles(x86)%\MSBuild\Microsoft.Cpp

vs-android is released under the zlib license. http://en.wikipedia.org/wiki/Zlib_License

Copyright (c) 2014 Gavin Pugh http://www.gavpugh.com/

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.