- What is a good BASIC compiler for Mac OSX? QB64 isn't exactly pretty, but it's a dialect of QBasic, with mac, windows, and linux IDEs, and it can (with tie ins to eclipse) compile for android as well.
- Apple mac os x c compiler free download - Apple Mac OS X Mavericks, Apple Mac OS X Yosemite, Apple Mac OS X Snow Leopard, and many more programs.
Apr 03, 2014 C Compiler for Mac using Xcode. The most recommended way to get a C compiler for your Mac is to use Xcode. This uses gcc, the popular open source C compiler. The details vary for each version of OS X. We’ll go through the recent versions here. You will have to register as an apple developer to get access to these tools.
Developer(s) | Intel |
---|---|
Stable release | 19.1.4 (XE 2020) / October 22, 2020; 1 day ago[1][2] |
Operating system | Windows, Mac, Linux, FreeBSD |
Type | Compiler |
License | Trialware |
Website | software.intel.com/en-us/intel-compilers |
Developer(s) | Intel |
---|---|
Stable release | |
Operating system | Windows, OS X |
Type | Compiler |
License | Trialware |
Website | software.intel.com/c-compiler-android |
Intel C++ Compiler, also known as icc or icl, is a group of C and C++compilers from Intel available for Windows, Mac, Linux, FreeBSD[4] and Intel-based Android devices.
Overview[edit]
The compilers generate optimized code for IA-32 and Intel 64 architectures, and non-optimized code for non-Intel but compatible processors, such as certain AMD processors. A specific release of the compiler (11.1) is available for development of Linux-based applications for IA-64 (Itanium 2) processors.
The 14.0 compiler added support for Intel-based Android devices and optimized vectorization and SSE Family instructions for performance. The 13.0 release added support for the Intel Xeon Phi coprocessor. It continues support for automatic vectorization, which can generate SSE, SSE2, SSE3, SSSE3, SSE4, AVX and AVX2SIMD instructions, and the embedded variant for Intel MMX and MMX 2.[5] Use of such instruction through the compiler can lead to improved application performance in some applications as run on IA-32 and Intel 64 architectures, compared to applications built with compilers that do not support these instructions.
Intel compilers support Cilk Plus (removed in 19.1), which is a capability for writing vectorized and parallel code that can be used on IA-32 and Intel 64 processors or which can be offloaded to Xeon Phi coprocessors. They also continue support for OpenMP 4.0, symmetric multiprocessing, automatic parallelization, and Guided Auto-Parallization (GAP). With the add-on Cluster OpenMP capability, the compilers can also automatically generate Message Passing Interface calls for distributed memory multiprocessing from OpenMP directives.
Intel C++ is compatible with Microsoft Visual C++ on Windows and integrates into Microsoft Visual Studio. On Linux and Mac, it is compatible with GNU Compiler Collection (GCC) and the GNU toolchain. Intel C++ Compiler for Android is hosted on Windows, OS X or Linux and is compatible with the Android NDK, including gcc and the Eclipse IDE. Intel compilers are known for the application performance they can enable as measured by benchmarks, such as the SPEC CPU benchmarks.
Optimizations[edit]
Intel compilers are optimized to computer systems using processors that support Intel architectures. They are designed to minimize stalls and to produce code that executes in the fewest possible number of cycles. The Intel C++ Compiler supports three separate high-level techniques for optimizing the compiled program: interprocedural optimization (IPO), profile-guided optimization (PGO), and high-level optimizations (HLO). The Intel C++ compiler in the Parallel Studio XE products also supports tools, techniques and language extensions for adding and maintaining application parallelism on IA-32 and Intel 64 processors and enables compiling for Intel Xeon Phi processors and coprocessors.
Profile-guided optimization refers to a mode of optimization where the compiler is able to access data from a sample run of the program across a representative input set. The data would indicate which areas of the program are executed more frequently, and which areas are executed less frequently. All optimizations benefit from profile-guided feedback because they are less reliant on heuristics when making compilation decisions.
High-level optimizations are optimizations performed on a version of the program that more closely represents the source code. This includes loop interchange, loop fusion, loop fission, loop unrolling, data prefetch, and more.[6]
Interprocedural optimization applies typical compiler optimizations (such as constant propagation) but using a broader scope that may include multiple procedures, multiple files, or the entire program.[7]
David Monniaux has criticized Intel's compiler for applying, by default, floating-point optimizations which are not allowed by the C standard and which require special flags with other compilers such as gcc.[8]
Architectures[edit]
- x86-64 (Intel 64 and AMD64)
- IA-64 (Itanium 2)
Description of packaging[edit]
Except for the Intel Bi-Endian C++ Compiler, Intel C++ compilers are not available in standalone form. They are available in suites:
- Intel Parallel Studio XE for development of technical, enterprise, and high-performance computing applications on Windows, Linux and Mac
- Intel System Studio for development of system and app software for embedded systems or devices running Windows, Linux or Android
The suites include other build tools, such as libraries, and tools for threading and performance analysis.
History since 2003[edit]
Compiler version | Release date | Major new features |
---|---|---|
Intel C++ Compiler 8.0 | December 15, 2003 | Precompiled headers, code-coverage tools. |
Intel C++ Compiler 8.1 | September, 2004 | AMD64 architecture (for Linux). |
Intel C++ Compiler 9.0 | June 14, 2005 | AMD64 architecture (for Windows), software-based speculative pre-computation (SSP) optimization, improved loop optimization reports. |
Intel C++ Compiler 10.0 | June 5, 2007 | Improved parallelizer and vectorizer, Streaming SIMD Extensions 4 (SSE4), new and enhanced optimization reports for advanced loop transformations, new optimized exception handling implementation. |
Intel C++ Compiler 10.1 | November 7, 2007 | New OpenMP* compatibility runtime library: if you use the new OpenMP RTL, you can mix and match with libraries and objects built by Visual C++. To use the new libraries, you need to use the new option '-Qopenmp /Qopenmp-lib:compat' on Windows, and '-openmp -openmp-lib:compat' on Linux. This version of the Intel compiler supports more intrinsics from Visual Studio 2005. VS2008 support - command line only in this release. The IDE integration was not supported yet. |
Intel C++ Compiler 11.0 | November 2008 | Initial C++11 support. VS2008 IDE integration on Windows. OpenMP 3.0. Source Checker for static memory/parallel diagnostics. |
Intel C++ Compiler 11.1 | June 23, 2009 | Support for latest Intel SSE SSE4.2, AVX and AES instructions. Parallel Debugger Extension. Improved integration into Microsoft Visual Studio, Eclipse CDT 5.0 and Mac Xcode IDE. |
Intel C++ Composer XE 2011 up to Update 5 (compiler 12.0) | November 7, 2010 | Cilk Plus language extensions, Guided Auto-Parallelism, Improved C++11 support.[9] |
Intel C++ Composer XE 2011 Update 6 and above (compiler 12.1) | September 8, 2011 | Cilk Plus language extensions updated to support specification version 1.1 and available on Mac OS X in addition to Windows and Linux, Threading Building Blocks updated to support version 4.0, Apple blocks supported on Mac OS X, improved C++11 support including support for Variadic templates, OpenMP 3.1 support. |
Intel C++ Composer XE 2013 (compiler 13.0) | September 5, 2012 | Linux-based support for Intel Xeon Phi coprocessors, support for Microsoft Visual Studio 12 (Desktop), support for gcc 4.7, support for Intel AVX 2 instructions, updates to existing functionality focused on improved application performance.[10] |
Intel C++ Composer XE 2013 SP1 (compiler 14.0) | September 4, 2013 | Online installer; support for Intel Xeon Phi coprocessors; preview Win32 only support for Intel graphics; improved C++11 support |
Intel C++ Composer XE 2013 SP1 Update 1 (compiler 14.0.1) | October 18, 2013 | Japanese localization of 14.0; Windows 8.1 and Xcode 5.0 support |
Intel C++ Compiler for Android (compiler 14.0.1) | November 12, 2013 | Hosted on Windows, Linux, or OS X, compatible with Android NDK tools including the gcc compiler and Eclipse |
Intel C++ Composer XE 2015 (compiler 15.0) | July 25, 2014 | Full C++11 language support; Additional OpenMP 4.0 and Cilk Plus enhancements |
Intel C++ Composer XE 2015 Update 1 (compiler 15.0.1) | October 30, 2014 | AVX-512 support; Japanese localization |
Intel C++ 16.0 | August 25, 2015 | Suite-based availability (Intel Parallel Studio XE, Intel System Studio) |
Intel C++ 17.0 | September 15, 2016 | Suite-based availability (Intel Parallel Studio XE, Intel System Studio) |
Intel C++ 18.0 | January 26, 2017 | Suite-based availability (Intel Parallel Studio XE, Intel System Studio) |
Intel C++ 19.0 | April 3, 2018 | Suite-based availability (Intel Parallel Studio XE, Intel System Studio) |
Flags and manuals[edit]
Documentation can be found at the Intel Software Technical Documentation site.
Windows | Linux, macOS & FreeBSD | Comment |
---|---|---|
/Od | -O0 | No optimization |
/O1 | -O1 | Optimize for size |
/O2 | -O2 | Optimize for speed and enable some optimization |
/O3 | -O3 | Enable all optimizations as O2, and intensive loop optimizations |
/arch:SSE3 | /-msse3 | Enables SSE3, SSE2 and SSE instruction sets optimizations for non-Intel CPUs[11] |
/fast | -fast | Shorthand. On Windows this equates to '/O3 /Qipo /QxHost /Opred-div-' ; on Linux '-O3 -ipo -static -xHOST -no-prec-div'. Note that the processor specific optimization flag (-xHOST) will optimize for the processor compiled on—it is the only flag of -fast that may be overridden |
/Qprof-gen | -prof_gen | Compile the program and instrument it for a profile generating run |
/Qprof-use | -prof_use | May only be used after running a program that was previously compiled using prof_gen. Uses profile information during each step of the compilation process |
Debugging[edit]
The Intel compiler provides debugging information that is standard for the common debuggers (DWARF 2 on Linux, similar to gdb, and COFF for Windows). The flags to compile with debugging information are /Zi on Windows and -g on Linux. Debugging is done on Windows using the Visual Studio debugger and, on Linux, using gdb.
While the Intel compiler can generate a gprof compatible profiling output, Intel also provides a kernel level, system-wide statistical profiler called Intel VTune Profiler. VTune can be used from a command line or thru an included GUI on Linux or Windows. It can also be integrated into Visual Studio on Windows, or Eclipse on Linux). In addition to the VTune profiler, there is Intel Advisor that specializes in vectorization optimization, offload modeling, flow graph design and tools for threading design and prototyping.
Intel also offers a tool for memory and threading error detection called Intel Inspector XE. Regarding memory errors, it helps detect memory leaks, memory corruption, allocation/de-allocation of API mismatches and inconsistent memory API usage. Regarding threading errors, it helps detect data races (both heap and stack), deadlocks and thread and synch API errors.
Reception[edit]
Intel and third parties have published benchmark results to substantiate performance leadership claims over other commercial, open-source and AMD compilers and libraries on Intel and non-Intel processors. Intel and AMD have documented flags to use on the Intel compilers to get optimal performance on Intel and AMD processors.[12][13] Nevertheless, the Intel compilers have been known to use sub-optimal code for processors from vendors other than Intel. For example, Steve Westfield wrote in a 2005 article at the AMD website:[14]
Intel 8.1 C/C++ compiler uses the flag -xN (for Linux) or -QxN (for Windows) to take advantage of the SSE2 extensions. For SSE3, the compiler switch is -xP (for Linux) and -QxP (for Windows). ... With the -xN/-QxN and -xP/-QxP flags set, it checks the processor vendor string—and if it's not 'GenuineIntel', it stops execution without even checking the feature flags. Ouch!
The Danish developer and scholar Agner Fog wrote in 2009:[15]
The Intel compiler and several different Intel function libraries have suboptimal performance on AMD and VIA processors. The reason is that the compiler or library can make multiple versions of a piece of code, each optimized for a certain processor and instruction set, for example SSE2, SSE3, etc. The system includes a function that detects which type of CPU it is running on and chooses the optimal code path for that CPU. This is called a CPU dispatcher. However, the Intel CPU dispatcher does not only check which instruction set is supported by the CPU, it also checks the vendor ID string. If the vendor string is 'GenuineIntel' then it uses the optimal code path. If the CPU is not from Intel then, in most cases, it will run the slowest possible version of the code, even if the CPU is fully compatible with a better version.
This vendor-specific CPU dispatching (function multi-versioning) decreases the performance on non-Intel processors of software built with an Intel compiler or an Intel function library – possibly without the knowledge of the programmer. This has allegedly led to misleading benchmarks,[15] including one incident when changing the CPUID of a VIA Nano significantly improved results.[16] A legal battle between AMD and Intel over this and other issues has been settled in November 2009.[17] In late 2010, AMD settled a US Federal Trade Commissionantitrust investigation against Intel.[18]
The FTC settlement included a disclosure provision where Intel must:[19]
publish clearly that its compiler discriminates against non-Intel processors (such as AMD's designs), not fully utilizing their features and producing inferior code.
In compliance with this rule, Intel added an 'optimization notice' to its compiler descriptions stating that they 'may or may not optimize to the same degree for non-Intel microprocessors' and that 'certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors'. It says that:[20]
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.
As reported by The Register[21] in July 2013, Intel was suspected of 'benchmarksmanship', when it was shown that the object code produced by the Intel compiler for the AnTuTu Mobile Benchmark omitted portions of the benchmark which showed increased performance compared to ARM platforms.
See also[edit]
- Intel Integrated Performance Primitives (IPP)
- Intel Data Analytics Acceleration Library (DAAL)
- Intel Math Kernel Library (MKL)
- Intel Threading Building Blocks (TBB)
- VTune Amplifier
- Intel Developer Zone (Intel DZ; support and discussion)
References[edit]
- ^'Intel® C++ Compiler Release Notes and New Features'. software.intel.com.
- ^'Intel® C++ Compiler 19.1 Release Notes'. software.intel.com.
- ^'Intel C++ Compiler for Android documentation'. software.intel.com.[citation not found]
- ^'Intel® System Studio 2016 for FreeBSD* | Intel® Software'. software.intel.com. Retrieved 2018-03-15.
- ^A. J. C. Bik, The Software Vectorization Handbook (Intel Press, Hillsboro, OR, 2004), ISBN0-9743649-2-4.
- ^The Software Optimization Cookbook, High-Performance Recipes for IA-32 Platforms, Richard Gerber, Aart J.C. Bik, Kevin B. Smith, and Xinmin Tian, Intel Press, 2006
- ^Intel C++ Compiler XE 13.0 User and Reference Guides
- ^The pitfalls of verifying floating-point computations, by David Monniaux, also printed in ACM Transactions on programming languages and systems (TOPLAS), May 2008; section 4.3.2 discusses nonstandard optimizations.
- ^This note is attached to the release in which Cilk Plus was introduced. This ULR points to current documentation: http://software.intel.com/en-us/intel-composer-xe/
- ^Intel C++ Composer XE 2013 Release Notes[1]http://software.intel.com/en-us/articles/intel-c-composer-xe-2013-release-notes/
- ^'Intel® Compilers | Intel® Developer Zone'. Intel.com. 1999-02-22. Retrieved 2012-10-13.
- ^[2]Archived March 23, 2010, at the Wayback Machine
- ^'Archived copy'(PDF). Archived from the original(PDF) on 2011-03-22. Retrieved 2011-03-30.CS1 maint: archived copy as title (link)
- ^'Your Processor, Your Compiler, and You: The Case of the Secret CPUID String'. Archived from the original on 2012-01-05. Retrieved 2011-12-11.
- ^ ab'Agner`s CPU blog - Intel's 'cripple AMD' function'. www.agner.org.
- ^Hruska, Joel (29 July 2008). 'Low-end grudge match: Nano vs. Atom'. Ars Technica.
- ^'Settlement agreement'(PDF). download.intel.com.
- ^'Intel and U.S. Federal Trade Commission Reach Tentative Settlement'. Newsroom.intel.com. 2010-08-04. Retrieved 2012-10-13.
- ^'FTC, Intel Reach Settlement; Intel Banned From Anticompetitive Practices'. Archived from the original on 2012-02-03. Retrieved 2011-10-20.
- ^'Optimization Notice'. Intel Corporation. Retrieved 11 December 2013.
- ^'Analyst: Tests showing Intel smartphones beating ARM were rigged'.
External links[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Intel_C%2B%2B_Compiler&oldid=984992801'
Silent Installation Guide for Intel Compilers for Mac OS* X Versions 14.x, 13.x, 12.x, 11.x, 11.x and 10.1
Navigation
Linux and Mac OS X Compilers Installation Help Center: /en-us/articles/intel-compilers-linux-installation-help
This guide presents silent installation instructions for current and previous versions of Intel compilers. Newer compilers are described first, scroll down for version 11.x or older.
Silent Installation Guide for Intel Compilers for Mac OS* X Versions 14.x, 13.x, and 12.x
Free Download C++ Compiler For Mac Os X
Here are the steps you need to follow to install the Intel Composer XE for OS X* version 2013 SP1 aka '14.0' in silent mode.
Step 0) Confirm that the userID for the installation has 'sudo' priviledge. If you are unfamiliar with the 'sudo' command please research that command on the internet to become familiar with it's use. Test your sudo priviledge with a simple sudo command such as 'sudo pwd' or 'sudo ls -l'
Step 0) Confirm that the userID for the installation has 'sudo' priviledge. If you are unfamiliar with the 'sudo' command please research that command on the internet to become familiar with it's use. Test your sudo priviledge with a simple sudo command such as 'sudo pwd' or 'sudo ls -l'
Step 1) Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. OR If you are working from a terminal window, use the hdiutil command to mount the compiler installer disk image (.dmg)
2013 SP1 Example:
2013 SP1 Example:
Disk image mounts under
- /Volumes/m_fcompxe_2013_sp1.u.vvv (for the Fortran Composer XE 2013 SP1)
- /Volumes/m_ccompxe_2013_sp1.u.vvv (for the C++ Composer XE 2013 SP1)
Mount the image
- sudo hdiutil attach m_fcompxe_2013_sp1.u.vvv.dmg
- sudo hdiutil attach m_ccompxe_2013_sp1.u.vvv.dmg
where 'u' is the update number ( 0, 1, 2, 3, etc) and where 'vvv' is the specific version ( 2013_sp1.2.142 is Update 2, version 142 for example)
Step 2) Start a 'Terminal' program from Utilities group (if you have not done so already.
Step 3) Using 'Terminal', change directory to the /Packages folder:
Step 2) Start a 'Terminal' program from Utilities group (if you have not done so already.
Step 3) Using 'Terminal', change directory to the /Packages folder:
2013 SP1 Example:
- cd /Volumes/m_ccompxe_2013_sp1.X.YYY/Packages
- cd /Volumes/m_fcompxe_2013_sp1.X.YYY/Packages
Step 4) Use 'sudo' to run the Intel installer 'i_install': ./i_install with the silent install options.
Usage: ./i_install [OPTIONS]
For Version 2013 SP1: usage: sudo ./i_install [-s or -h] [-f 'license file or folder or port@host'] or [-sn 'serialnumber'] -xd 'xcode folder' -l 'log file' -it '[1/2]' -sd '[yes/no]' -eula 'accept'
User can provide a valid serial number following the -sn option or a license file with the complete path or port@host for server license following the -f option.
Usage: ./i_install [OPTIONS]
For Version 2013 SP1: usage: sudo ./i_install [-s or -h] [-f 'license file or folder or port@host'] or [-sn 'serialnumber'] -xd 'xcode folder' -l 'log file' -it '[1/2]' -sd '[yes/no]' -eula 'accept'
User can provide a valid serial number following the -sn option or a license file with the complete path or port@host for server license following the -f option.
Required Options
- -s : to indicate execute in silent mode
- -l : [optional] to provide a install log file (this file will be created '/tmp' folder. Do not use any path information, just some simple name like 'install.log'.
- -f : -licfile Install silently using the license file provided on the command line. Include the full path to the .lic license file on your system. Typically these are stored in directory /Users/Shared/Library/Application Support/Intel/Licenses/<file>.lic
- Port@host Install silently using the server license available at host
- -sn, -sn Install silently using the serial number provided on the command line
- -eula 'accept' to confirm that you have read the End User Licensing Agreement and have accepted the license conditions. By using silent installation you must accept the EULA and by using the silent installation you have agreed to those terms.
More required Options for all compilers Version 11.1 and above
- -id <install_dir> 'install directory', default install folder is /opt/intel
- Silent install utility installs all the packages bundled in the meta package.
- To set the top level install folder for these packages one can use this option
- -xd : 'xcode folder' ( provide Xcode IDE folder for compiler to be integrated with) - /Applications/Xcode.app for example or /Developer/XCode
More required Options for all compilers Version 12.0 and above (Composer XE 2011, Composer XE 2013, Composer XE 2013 SP1)
12.0 and 12.1 versions:
12.0 and 12.1 versions:
- -it: install type; 1. commandline install 2. xcode integration 3. both, command line and xcode environment.
- User has option to install either command line alone and/or integrate with xcode IDEenviromen
- Default install type is 3
More required options for all compilers version 13.0, 13.1, and 14.0: Composer XE 2013 and 2013 SP1 versions:
- -it: install type; 1. Command line install 2. both, command line and Xcode environment.
- User has option to install either command line alone or integrate with Xcode IDE enviroment
- Default install type is 2
- -sd: indicates agreement to participate in Intel(R) Software Improvement Program, by default is 'no'
Silent Installation Guide for Intel Compilers for Mac OS* X Version 11.x
Here are the steps you need to follow to install the Intel Compilers for Mac OS X* version 11.0 and higher in silent mode.
Step 0) Login as an administrative user or root. If you have sudo priviledge, become root user in a Terminal window with:
- sudo bash
- and enter your user password, then enter command
- su -
Step 1) Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. OR If you are working from a terminal window, use the hdiutil command to mount the compiler installer disk image (.dmg)
11.0 Example (11.1 is similar):
Disk image mounts under
- /Volumes/m_cprof_p_11.0.0xx (for the 11.0 Fortran Compiler) or
- /Volumes/m_cproc_p_11.0.0xx (for the 11.0 C++ Compiler)
Mount image with
- hdiutil attach m_cprof_p_11.0.0xx.dmg
- hdiutil attach m_cproc_p_11.0.0xx.dmg
12.0 Example:
Disk image mounts under
- /Volumes/m_fcompxe_2011.u.vvv (for the 12.0 Fortran Compiler) or
- /Volumes/m_ccompxe_2011.u.vvv (for the 12.0 C++ Compiler)
Mount image with
- hdiutil attach m_fcompxe_2011.u.vvv.dmg
- hdiutil attach m_ccompxe_2011.u.vvv.dmg
![Free c++ compiler for mac os x Free c++ compiler for mac os x](/uploads/1/2/6/6/126672272/176058289.jpg)
where 'u' is the update number ( 0, 1, 2, 3, etc) and where 'vvv' is the specific version ( 2011.2.142 is Update 2, version 142 for example).
Step 2) Start a 'Terminal' program from Utilities group (if you have not done so already. Do this as root user or use the command 'sudo bash' to become root user)
Step 3) Using 'Terminal' as root user, change directory to the /Plugins folder:
11.0 (similarly for 11.1):
Change directory to the 'Plugins' folder inside /Volumes/m_cprof_p_11.0.0xx
For example:
- cd /Volumes/m_cproc_p_11.0.0xx/m_cproc_p_11.0.0xx.mpkg/Contents/Plugins
- cd /Volumes/m_cprof_p_11.0.0xx/m_cproc_p_11.0.0xx.mpkg/Contents/Plugins
12.0:
- cd /Volumes/m_ccompxe_2011.2.142/m_ccompxe_2011.2.142.mpkg/Contents/Plugins
- cd /Volumes/m_fcompxe_2011.2.142/m_fcompxe_2011.2.142.mpkg/Contents/Plugins
Step 4) Run installer 'i_install': ./i_install with the silent install options.
Usage: ./i_install [OPTION]
For version 11.0: usage: ./i_install [-s or -h] -l 'log file' -f 'license file or folder or port@host' -eula 'accept'
For version 11.1: usage: ./i_install [-s or -h] -l 'log file' -f 'license file or folder or port@host' -sn 'serialnumber' -xd 'xcode folder' -id 'install folder' -eula 'accept'
For Version 12.0: usage: ./i_install [-s or -h] -l 'log file' [-f 'license file or folder or port@host'] or [-sn 'serialnumber'] -it '[1/2/3]'-xd 'xcode folder' -id 'install folder' -eula 'accept'
User can provide a valid serial number following the -sn option or a license file with the complete path or port@host for server license following the -f option.
Required Options
- -s : to indicate execute in silent mode
- -l : [optional] to provide a install log file (this file will be created '/tmp' folder
- -f : -licfile Install silently using the license file provided on the command line.
- Port@host Install silently using the server license available at host
- -sn, -sn Install silently using the serial number provided on the command line
Additional Options, Version 11.1 and above
- -id <install_dir> 'install directory', default install folder is /opt/intel
- Silent install utility installs all the packages bundled in the meta package.
- To set the top level install folder for these packages one can use this option
- If install_dir is provided then the mounted system has to be writable for silent installs
- If the mounted volume is not writable, then user gets'Seems mounted volume is read only file system. Use 'hdiutil attach '<disk-image-name>.dmg' -readwrite -shadow' command, to mount the disk image', message and aborts silent install.
- -xd : 'xcode folder' ( provide xcode IDE folder for compiler to be intgegared with)
Additional Options, Version 12.0 and above
- -it: install type; 1. commandline install 2. xcode integration 3. both, command line and xcode environment.
- User has option to install either command line alone and/or integrate with xcode IDEenviroment
- Default install type is 3
- -h Display the silent install usage.
Examples:
Log File
Option, '-l mylog_file' creates a install log file 'tmp/mylog_file', if this argument is not given then'/tmp/pset.log' file is created for logs.
Silent Installation Guide for Intel Compilers for Mac OS* X Version 10.1
Here are the steps you need to follow to install the Intel Compilers for Mac OS X* version 10.1 in silent mode.
- Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. If you are working from a terminal window, this command will mount the compiler installer disk image under /Volumes/m_fc_p_10.1.0xx (for the Fortran Compiler) or /Volumes/m_cc_p_10.1.0xx (for the C++ compiler)
- hdiutil attach m_fc_p_10.1.0xx.dmg
- hdiutil attach m_cc_p_10.1.0xx.dmg
- Start a 'Terminal' program from Utilities group (if you have not done so already). Using 'Terminal' do the following:
- Copy the contents of the mounted image to a local folder, for example:
- cp -pR /Volumes/m_fc_p_10.1.00x /Users/f_fc_p_10.1.00x (or the similar command for m_cc_p_10.1.0xx)
- Change directory to the local 'instman' folder inside the folder you copied in (a), for example:
- cd /Users/f_fc_p_10.1.00x/instman
- Export DYLD_LIBRARY_PATH=<instman folder>, for example:
- export DYLD_LIBRARY_PATH=/Users/f_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
- (optional) Make changes to ‘si_issa.xml' configuration file to change the default settings, see details below.
- Run: ./si_secore with the silent install options. Usage: /si_secore [OPTION]
The user must provide a valid serial number following the -sn option and a license file with the complete path following the --licfile option. -n, -sn Install silently using the serial number provided on the command line. The other settings will come from 'si_issa.xml' file in the instman folder or from a custom config file, specified as -c 'your config' on the command line.
- -l, -licfile Install silently using the license file provided on the command line. The other settings will come from 'si_issa.xml' file present in the instman folder or from the -c 'your config' file provided on the command line.
- -c Use ISSA and install parameters that are supplied through this configuration file.
- -h Display the silent install usage.
Precedence Order for Parameters
- If both -sn 'SN' and the -c 'CF' options are provided, the serial number provided via command line overrides the serial number specified in the <SerialNumber> value in the configuration file.
- If both -licfile 'LF' and the -c 'CF' options are provided, the license file provided via command line overrides the license file specified in the <LicenseFile> value in the configuration file.
- If both <SerialNumber> and <LicenseFile> values are provided in the configuration file or as command-line options, silent install will first copy the license file, validate and proceed with the install; if install fails, it will follow the serial number option path.
Configuration File
Free C++ Compiler For Mac Os X
The default configuration file 'si_issa.xml' is available in the ‘instman' folder. You can use the script file 'pre_sinstall.sh' available in the 'instman' folder to generate an silent install config file. Here is an example of the format of this configuration file
Note: the pkg_id attribute under <Package pkg_id='1'> will set the order in which the tools will be installed. You can change the install order based on dependencies between installed packages. Include the <Proxy> section only if a web proxy server is required to reach the Intel® Software Development Products Registration Center web server.
Examples:
Log File
To create a log file, create a directory named 'WorkArea' within the 'instman' folder. Rerun the installation, and files will be created in the 'WorkArea' folder. The most important file will be secore.log, which is a transcript of the ISSA session.
Silent Install Using ‘sudo'
Users utilizing the ‘sudo' command to perform a silent install need to modify the above procedure. By default, sudo will not preserve the user's DYLD_LIBRARY_PATH setting. The following silent install procedure should be used by sudo users:
To install the compiler with sudo in the 'silent' mode with an interactive shell
To create a log file, create a directory named 'WorkArea' within the 'instman' folder. Rerun the installation, and files will be created in the 'WorkArea' folder. The most important file will be secore.log, which is a transcript of the ISSA session.
Silent Install Using ‘sudo'
Users utilizing the ‘sudo' command to perform a silent install need to modify the above procedure. By default, sudo will not preserve the user's DYLD_LIBRARY_PATH setting. The following silent install procedure should be used by sudo users:
To install the compiler with sudo in the 'silent' mode with an interactive shell
- Mount the product dmg file with required content using Finder, for example, by double-clicking on the dmg file.
- Start a Terminal program from the Utilities group. Using Terminal, copy the contents of the mounted image to a local folder, for example
- cp -pR /Volumes/m_fc_p_10.1.00x /Users/m_fc_p_10.1.0xx
- Change directory to the local instman folder inside the folder you copied in (a), for example:
- cd /Users/m_fc_p_10.1.00x/instman
- Start a shell session under bash, for example:
- sudo /bin/bash
- Export DYLD_LIBRARY_PATH=<instman folder>, for example:
- export DYLD_LIBRARY_PATH=/Users/m_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
- (optional) Make changes to si_issa.xml configuration file to change the default settings, see details below.
- Run ./si_sicore with options as described above.
To install the compiler with sudo in the 'silent' mode with minimal interaction
The following method uses sudo in a mode suitable for scripted automation.
The following method uses sudo in a mode suitable for scripted automation.
- Start a Terminal program from the Utilities, or create a user shell (rsh, X11, etc)
- Change directories to a working area where the user has write permission. For example, cd /Users/<my user> ,where this is the home directory of user <my user>. This example assumes the user has downloaded or copied the compiler disk image (.dmg) file to this user home directory /Users/<my user>/m_fc_p_10.1.0xx.dmg where '0xx' is the compiler minor version.
- Mount the compiler disk image. Assumes compiler .dmg file is in your current directory. This command will mount the compiler installer disk image under /Volumes/m_fc_p_10.1.0xx: sudo hdiutil attach m_fc_p_10.1.0xx.dmg
- Copy the contents of the mounted image to a local folder where you have write permission. For example, if your current directory is user writeable: cp -pR /Volumes/m_fc_p_10.1.0xx /Users/<my user> , where '<my user>' is replaced by your login or user name.
- Change directories to /Users/<my users>/m_fc_p_10.1.0xx/instman created by the previous copy command: cd /Users/<my user>/m_fc_p_10.1.0xx/instman
- Use sudo to run the installer, using one of two possible methods, where '<options>' are replaced by si_secore options described above.
- sudo env DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ./si_secore <options>
- sudo -c 'DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ; ./si_secore <options> '
- For example, to use the serial number XXXX-XXXXXX to install:
- sudo -c 'DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ; ./si_secore -n XXXX-XXXXXX '
- (optional) Remove the compiler installation files. For example,
- cd /Users/<my user>
- rm -Rf m_fc_p_10.1.0xx
- (optional) Unmount the compiler installation image. For example, sudo hdiutil unmount /Volumes/m_fc_p_10.1.0xx
- Finally, to truly make this sequence suitable for scripting, you can pass your password to the sudo commands above using the -S option to sudo. For example, echo ‘MyPassword' | sudo -S <options> <command> , where ‘MyPassword' is your user password used to run sudo command.
Note
C 2b 2b Compiler For Mac Os X
As noted in the Intel® Software Development Product End User License Agreement, the Intel® Software Development Product you install will send Intel the product’s serial number and other system information to help Intel improve the product and validate license compliance. No personal information will be transmitted.