Prior to Intel® Compiler 15.0 in the offload compilation model, the binaries targeting the Intel MIC Architecture were generated as dynamic libraries (.so). Dynamic libraries do not need all referenced variables or routines to be resolved during linking as these can be resolved during load time. This behavior could mask some missing variable or routine in the application resulting in a failure during load time. In order to identify and resolve all missing symbols at link time, option "-z defs" must be provided to the linker.
The problem occurs when performing a custom installation of Intel(R) Parallel Studio XE 2016 on a Japanese version of Windows* OS where the custom installation specifies an installation path that contains non-English characters. This results in any documents selected from the Microsoft Visual Studio* "Help > Intel Compilers and Libraries" pull down menu to fail to launch and the browser's default page appearing instead. Workarounds:
When building an application that uses the Boost libraries with the Intel® C++ Compiler, you may get linker errors like the ones shown below due to incorrect libraries being linked to the application:
Known Issues for the Multi-OS Engine including Runtime, Apple iOS* API Bindings, Integrationg with Android Studio, Layout Editor, Local build, Remote build, Installation and UI Binding Generator.
In order to use the Intel® C++ or Fortran Compiler to develop for Windows* targets using Microsoft Visual Studio 2015*, it is necessary to install the 'Common Tools for Visual C++ 2015' component from Visual Studio. This component is not installed by default. The installation will detect the missing component and provide a warning, but the installation can still proceed. The component may be installed when Microsoft Visual Studio 2015* is first installed, or may be installed later.
Tips and tricks for using the Intel® RealSense™ SDK and cameras for 3D scanning.