The Intel® C++ Compiler for Android* integrates itself into the vs-android software. vs-android enables the Microsoft Visual Studio* build system to compile and link Android C/C++ projects. A working vs-android installation is required in order to use the Intel® C++ Compiler for Android within Microsoft Visual Studio*.
Download the vs-android plugin first. You find a download link on the project page: https://code.google.com/p/vs-android/ . Next follow the “A guide to installing vs-android” document (https://code.google.com/p/vs-android/wiki/Installation) to install “vs-android” and all required components.
Depending on the Intel® C++ Compiler version it's required to install a different version of the Android* NDK:
32-bit version of the Android* NDK must be installed to use Intel® C++ Compiler version 15.0 within Microsoft Visual Studio*.
64-bit version of the Android* NDK must be installed to use Intel® C++ Compiler version 16.0 within Microsoft Visual Studio*.
If vs-android is installed before you install Intel® C++ Compiler for Android, the compiler installation will be done in a way that supports the use of the vs-android toolset. In other words, if you have already installed vs-android into your Visual Studio installation, you will be able to use Visual Studio after you install the Intel Compiler
If you install vs-android plug-in after the Intel® C++ Compiler for Android you need to integrate the Intel Compiler to vs-android by following these steps:
Troubleshooting: If you see an error message saying "Access to path '...' is denied" you haven't started the vsa_updater.exe as administrator.
To use Intel® C++ Compiler for Android instead of GCC:
If you have installed Intel® Composer XE 2013 SP1, Update 1 or earlier, and integrated it into Visual Studio,* and then installed “vs_android,” Visual Studio will crash when you change the “Platform Toolset” to one of the available “x86 icc” toolchains. This bug is fixed in Intel® Composer XE 2013 SP1, Update 2.
-release-nosign: [echo] No key.store and key.alias properties found in build.properties. [echo] Please sign vs-android_samples\vs-android_samples\san-angeles\AndroidApk\bin\DemoActivity-release-unsigned.apk manually ... ... ,,, Deploying... ( Use 'Build -> Cancel' - to halt deploy ) C:\android\adt\sdk\platform-tools\adb.exe wait-for-device C:\android\adt\sdk\platform-tools\adb.exe install -r "vs-android_samples\san-angeles\AndroidApk\bin\DemoActivity-release.apk" can't find 'vs-android_samples\vs-android_samples\san-angeles\AndroidApk\bin\DemoActivity-release.apk' to install 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Platforms\Android\Microsoft.Cpp.Android.Targets(398,5): error MSB6006: "C:\android\adt\sdk\platform-tools\adb.exe" exited with code 1. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
This article applies to:
Products: Intel® System Studio, Intel® Integrated Native Developer Experience
Host OS/platforms: Windows (IA-32, Intel(R) 64)
Target OS/platforms: Android
Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.
Notice revision #20110804