source: issm/trunk/externalpackages/intel/readme@ 11237

How to install intel compiler to work on cygwin at the command line: 

This is what I got from the following post on google: 

-----------------------------------------------------
All necessary paths and environment variables are set if you put the Microsoft linker path in ICL.CFG, and open the Intel 
compiler command line window on the Start menu. Then you can run cygwin.bat so that bash inherits the ICL paths, 
without breaking ICL. You will sometimes get the bash warning about finding Windows style paths in the environment, 
but those are necessary for ICL and Microsoft link. Needless to say, the Windows environment variable forgetfulness
 point will be reached sooner with this setup.

After I run cygwin.bat, and try to run icl, it says:

link: invalid option -- o
Try `ling --help' for more information.

I verified that icl compiles without any problems before I run cygwin.bat

What am I missing?



This would indicate that you ignored my advice about icl.cfg, and so you are getting the wrong link.exe.  It should have said "link" not "ling."
For a VC9 installation, /windows/C/Program Files/Intel/Compiler/11.1/026/bin/ia32/icl.cfg:
-Qlocation,link,"C:\Program Files\Microsoft Visual Studio 9.0\VC\bin"
-Qprec-div -Qprec-sqrt -Qansi_alias
----------------------------------------------------------





So here is what you do: 
edit /cygdrive/c/IntelInstall/Compiler/11.1/026/bin/ia32/icl.cfg

add: 
-Qlocation,link,"C:\Program Files\Microsoft Visual Studio 9.0\VC\bin"
-Qprec-div -Qprec-sqrt -Qansi_alias


Then run the intel compiler command window. Go to C:\Cygwin and run Cygwin.bat. 
you are now running cygwin with the correct paths.  Type "export" at the command line, and figure out which variables have been set that relate to the intel compiler and visual studio environment. Build a file containing specific export commands and source it from your .bashrc. intel.sh is an example of such file on a Windows XP 32 build.