During compilation, the compiler reads the LIBRARY_PATH environment variable for static libraries it needs to link when building the executable. At runtime, the executable will link against dynamic libraries referenced in the LD_LIBRARY_PATH environment variable.
If you want to add a directory, /libs for example, to the LIBRARY_PATH, you can do either of the following:
Command line: prompt> export LIBRARY_PATH=/libs:$LIBRARY_PATH
Startup file: export LIBRARY_PATH=/libs:$LIBRARY_PATH
To compile file.cpp and link it with the library mylib.a, enter the following command:
//on Linux and macOS*
[invocation] file.cpp mylib.a With [invocation] being icc.
The compiler passes file names to the linker in the following order:
To the object file.
To any objects or libraries specified at the command line, in a response file, or in a configuration file.
To the Intel® C++ Compiler Classic Math Library, libimf.a.
By default, the Intel® C++ Compiler Classic uses the GNU* implementation of the C++ Standard Library (libstdc++) on OS* X v10.8, and libc++ implementation on OS* X v10.9. You can change the default using the -stdlib option:
-stdlib=libc++ //to switch to libc++ -stdlib=libstdc++ //to switch to libstdc++
The LIB environment variable contains a semicolon-separated list of directories in which the Microsoft* linker will search for library (.lib) files. The compiler does not specify library names to the linker, but includes directives in the object file to specify the libraries to be linked with each object.
For more information on adding library names to the response file and the configuration file, see Using Response Files and Using Configuration Files.
To specify a library name on the command line, you must first add the library's path to the LIB environment variable. Then, to compile file.cpp and link it with the library mylib.lib, enter the following command:
[invocation] file.cpp mylib.libWhere [invocation] is icc.
The Intel Compiler Math Libraries contain performance-optimized implementations for various Intel platforms. By default, the best implementation for the underlying hardware is selected at runtime. The library dispatch of multi-threaded code may lead to apparent data races, which may be detected by certain software analysis tools. However, as long as the threads are running on cores with the same CPUID, these data races are harmless and are not a cause for concern.