Silent Installation Guide for Intel Compilers for Mac OS* X Versions 14.x, 13.x, 12.x, 11.x, 11.x and 10.1

1. Mac Os X For Intel Headset
2. Mac Os X For Intel Hp Pavilion
3. Highly Compressed Mac Os X For Intel Pc
4. Mac Os X For Intel Hdmi
5. Mac Os X Intel Hd Graphics 2000

How to install mac os on windows pc? In this tutorial, lets discuss how to dual boot windows + apple mac os in your. Mac OS X For Intel. Building a computer with Intel's technology shouldn't prove too difficult for Apple's engineers, but one of the most important factors in the transition to Intel-based Macs will be, as Jobs himself put it, 'making Mac OS X sing on Intel processors'. Mac OS X 10.6 Snow Leopard was the first version of OS X to be built exclusively for Intel Macs, and the final release with 32-bit Intel Mac support. The name was intended to signal its status as an iteration of Leopard, focusing on technical and performance improvements rather than user-facing features; indeed it was explicitly branded to.

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

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 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:

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:

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.

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:

• -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

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.

1. 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
2. Start a 'Terminal' program from Utilities group (if you have not done so already). Using 'Terminal' do the following:
3. 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)
4. 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
5. Export DYLD_LIBRARY_PATH=<instman folder>, for example:
   • export DYLD_LIBRARY_PATH=/Users/f_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
6. (optional) Make changes to ‘si_issa.xml' configuration file to change the default settings, see details below.
7. 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

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

1. Mount the product dmg file with required content using Finder, for example, by double-clicking on the dmg file.
2. 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
3. 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
4. Start a shell session under bash, for example:
   • sudo /bin/bash
5. Export DYLD_LIBRARY_PATH=<instman folder>, for example:
   • export DYLD_LIBRARY_PATH=/Users/m_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
6. (optional) Make changes to si_issa.xml configuration file to change the default settings, see details below.
7. 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.

1. Start a Terminal program from the Utilities, or create a user shell (rsh, X11, etc)
2. 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.
3. 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
4. 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.
5. 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
6. 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 '
7. (optional) Remove the compiler installation files. For example,
   • cd /Users/<my user>
   • rm -Rf m_fc_p_10.1.0xx
8. (optional) Unmount the compiler installation image. For example, sudo hdiutil unmount /Volumes/m_fc_p_10.1.0xx
9. 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

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.

Mac Os X For Intel Headset

Using the Intel® Power Gadget API on Mac OS X*

Intel® Power Gadget for Mac* is a GUI application that provides real-time data on processor frequency and estimated processor power, and can log frequency, power, energy, and temperature data over time. Intel® Power Gadget also provides a C Application Programming Interface (API) for accessing this power and frequency data in your program. Intel® Power Gadget is also available for Windows* and Linux*. Intel® Power Gadget and the API are only supported on 2^nd generation and later Intel® Core processors, because previous processors do not support the necessary power Model Specific Registers (MSRs).

Intro to the Intel® Power Gadget API

The Intel® Power Gadget API is a framework (IntelPowerGadget .framework) that provides a C interface for reading current estimated processor power, current processor frequency, base frequency, thermal design power (TDP), current temperature, maximum temperature, timestamps, and elapsed time. It also provides logging functionality.

What You Need

To use the API you’ll need the Intel® Power Gadget for Mac* driver and framework. These are included in the Intel® Power Gadget installer, or as a standalone API installer. The driver is installed to /System/Library/Extensions/EnergyDriver.kext, and the framework is installed to /Library/Frameworks/IntelPowerGadget.framework.

To link with the Intel® Power Gadget API you simply need to include
–framework IntelPowerGadget in your link command.

Using the Intel® Power Gadget API

To begin you must initialize the library by calling IntelEnergyLibInitialize.

The most common use of the Intel® Power Gadget API is to read samples with ReadSample. The API supports sampling of specific Model Specific Registers (MSRs). Meta data on the sampled MSRs can be queried with GetNumMsrs, GetMsrName, and GetMsrFunc. GetNumMsrs returns the number of sampled MSRs; MSRs are given an ID from 0 to n-1, where n is the number returned by GetNumMsrs. The MSR ID is used to get data for a specific MSR with functions GetPowerData, GetMsrName, and GetMsrFunc.

Calling GetPowerData for each sampled MSR will provide you with the relevant data from that MSR. An MSR’s function (from GetMsrFunc) determines the amount and meaning of data returned from GetPowerData. MSRs with function 0 (frequency) return 1 result, which represents the frequency in megahertz. MSRs with function 1 (power) return 3 results, which represent the average power in watts, cumulative energy in Joules, and cumulative energy in milliwatt-hours. MSRs with function 2 (temperature) return 1 result, which represents the temperature in degrees Celsius. The Intel® Power Gadget API currently supports sampling with the following MSRs: processor frequency, estimated processor power, and package temperature. The currently supported MSR functions are: frequency (0), power (1), temperature (2).

ReadSample also reads the system time and Time Stamp Counter (TSC) at the time the sample is read. These values are available via GetSysTime and GetRDTSC; the time interval between samples is available (in seconds) via GetTimeInterval. Note that you must call ReadSample prior to calling GetPowerData, GetRDTSC, and GetTimeInterval, and that you must call ReadSample twice before calling GetTimeInterval and before getting power data (as opposed to frequency or temperature data) from GetPowerData, as they are computed using the difference between two samples.

The Intel® Power Gadget API also supports reading generic MSRs with ReadMSR, which returns the raw data from the MSR. However, note that specifying an invalid MSR address can crash your system and could potentially corrupt it. There is no method to determine if an MSR address is valid. The API supports reading common individual MSRs without having to specify the MSR address or read an entire sample; the supported functions are: GetIAFrequency, GetMaxTemperature, GetTemperature, and GetTDP.

The sample data from ReadSample can be logged to a file. Logging can be enabled at any time by calling StartLog, and subsequently disabled by calling StopLog. Note that the logged data isn’t written until StopLog is called. Both StartLog and StopLog cause an internal call to ReadSample.

Sampling Considerations

The frequency at which you read samples may have an impact on the accuracy of data. The instantaneous processor frequency can change significantly from moment to moment. Frequency data may be more meaningful if you sample often and average the frequency samples over time. The processor power is calculated by taking the difference between two samples, thus a shorter interval between samples will result in more fine-grained power data. However, the frequency at which you read samples may also impact the performance of the system. Using a very short frequency (e.g. less than 20 milliseconds) may result in significant overhead, and may also increase the power consumption of the system, both of which may reduce the usefulness of the data. The Intel® Power Gadget application uses a default sampling frequency of 50 milliseconds, and updates the GUI with averaged frequency and power data every second.

Example

Download the Xcode project for this example application here.

API Reference

Initializes the library and connects to the driver.

Returns the number of CPU packages on the system.

Returns the number of supported MSRs for bulk reading and logging.

Returns in szName the name of the MSR specified by iMsr. Note that the Windows version uses wchar_t.

Returns in pFuncID the function of the MSR specified by iMsrCurrently supported functions are: 0 = frequency, 1 = power, 2 = temperature.

Mac Os X For Intel Hp Pavilion

Reads the MSR specified by address on the package specified by iNode, and returns the value in value. Warning: Specifying an invalid MSR address can crash your system and could potentially corrupt it. There is no method to determine if an MSR address is valid.

Highly Compressed Mac Os X For Intel Pc

Reads the processor frequency MSR on the package specified by iNode, and returns the frequency in MHz in freqInMHz.

Reads the package power info MSR on the package specified by iNode, and returns the TDP in watts in TDP.

Reads the temperature target MSR on the package specified by iNode, and returns the maximum temperature in degrees Celsius in degreeC.

Reads the temperature MSR on the package specified by iNode, and returns the current temperature in degrees Celsius in degreeC.

Mac Os X For Intel Hdmi

Reads sample data from the driver for all the supported MSRs. Note that two calls to ReadSample are necessary to calculate power data, as power data is calculated using the difference between two samples.

Returns the system time as of the last call to ReadSample. The data returned in pSysTime is structured as follows:

Mac Os X Intel Hd Graphics 2000

pSysTime[63:32] = time in seconds

pSysTime[31:0] = time in nanoseconds

Returns in pTSC the processors time stamp counter as of the last call to ReadSample. Note that this function does not execute the rdtsc instruction directly, but instead returns the TSC from when the last sample was read.

Returns in pOffset the time in seconds that has elapsed between the two most recent calls to ReadSample.

Returns in pBaseFrequency the advertised processor frequency for the package specified by iNode.

Returns the data collected by the most recent call to ReadSample. The returned data is for the data on the package specified by iNode, from the MSR specified by iMSR. The data is returned in pResult, and the number of double results returned in pResult is returned in nResult. Frequency MSRs (function 0) return 1 result, which represents the frequency in megahertz. Power MSRs (function 1) return 3 results, which represent the average power in watts, cumulative energy in Joules, and cumulative energy in milliwatt-hours. Temperature MSRs (function 2) return 1 result, which represents the temperature in degrees Celsius.

Starts saving the data collected by ReadSample. When StopLog is called, this data will be written to the file specified by szFileName. Note that the Windows version uses wchar_t. StartLog will cause an initial call to ReadSample.

Stops saving data and writes all saved data to the file specified by the call to StartLog. StopLog will cause a final call to ReadSample.