Re: Configuring Intel Visual Fortran Composer XE 2011 ---> build environment window found

On Tue, Jan 25, 2011 at 9:43 AM, Bachman, William < [email protected]> wrote: > A NONMEM user informed me that the build environment window for Intel > Visual Fortran Composer XE 2011 is present in Windows 7. (It was just not > immediately evident because of a cosmetic change in the appearance of the > Start menu for Windows 7 by Microsoft.) Thanks CJ! > > To access the build environment: > > From the Start Menu -> All Programs -> Intel Parallel Studio XE 2011 -> > Command Prompt -> Parallel Studio XE with Intel Compiler XE v12.0 Update 1 -> > IA-32 Visual Studio 2010 mode > > or > > From the Start Menu -> All Programs -> Intel Parallel Studio XE 2011 -> > Command Prompt -> Parallel Studio XE with Intel Compiler XE v12.0 Update 1 > -> Intel64 Visual Studio 2010 mode > (the year reference to Visual Studio version in the above examples may be > different depending on your installation, e.g. 2008 instead of 2010.) > > You can use the build environment (without modification) to install and run > NONMEM if you ALWAYS intend to use the Intel build environment window for > running NONMEM. Otherwise, if you choose to or have a need to use a > "regular" command prompt, the instructions below will apply for configuring > the global system environment (and command prompt window) for NONMEM and > PDx-Pop. > > ------------------------------ > *From:* [email protected] [mailto:[email protected]] > *On Behalf Of *Bachman, William > *Sent:* Thursday, January 20, 2011 3:01 PM > *To:* [email protected] > *Subject:* [NMusers] Configuring Intel Visual Fortran Composer XE 2011 to > run NONMEM from the DOS command line on Windows 7 > > Configuring Intel Visual Fortran Composer XE 2011 to run NONMEM from the > DOS command line on Windows 7 > January 20, 2011 > > Incredibly, Intel made their newest compiler, Intel Visual Fortran Composer > XE 2011, even harder to use than previous versions. I was not able to find > a build environment window like the previous Intel versions that could be > used. So unless the build environment is there (and I just was too > impatient to keep looking for it), you must configure the system environment > variables to run the new compiler in a DOS window for use with NONMEM. The > following instructions were derived on a Windows 7 64-bit dual core Intel > system prior to installing NONMEM 7.2 beta on the system. > > 1. After installing Intel Visual Fortran Composer XE 2011 on the system, > open a DOS window (Command Prompt window). You will find that ifort.exe > is not recognized: > > C:\bill>ifort > 'ifort' is not recognized as an internal or external command, > operable program or batch file. > > 2. Next use the "set" command to write a file containing the system > environment before configuring it for the new compiler: > > C:\bill>set > beforeConfig.txt > > 3. Now, find the ifortvars.bat under the composer installation. It will > take some digging (and I recommend turning on file extensions to aid your > search). In my case, it was located at > > c:\Program Files (x86)\Intel\ComposerXE-2011\bin\ifortvars.bat > > The ifortvars.bat sets the environment for the compiler (but not > permanently, just for this instance of this window). > > 4. If you run the ifortvars.bat, you need to surround the command with > quotes because of the spaces in the path: > > C:\bill>"c:\Program Files (x86)\Intel\ComposerXE-2011\bin\ifortvars.bat" > Syntax: > ifortvars.bat <arch> [vs] > > <arch> must be is one of the following > ia32 : Set up for IA-32 host and target > ia32_intel64 : Set up for IA-32 host and Intel(R)64 target > intel64 : Set up for Intel(R) 64 host and target > If specified, <vs> must be one of the following > vs2005 : Set to use Microsoft Visual Studio 2005 > vs2008 : Set to use Microsoft Visual Studio 2008 > vs2008shell : Set to use Microsoft Visual Studio Shell 2008 > vs2010 : Set to use Microsoft Visual Studio 2010 > If <vs> is not specified, the version of Visual Studio detected at > install > time is used. > > Note that there is a required architecture argument (ia32, ia32_intel64, or > intel64) and an optional Visual Studio argument. If you don't know the > architecture, consult your IT department for help. > > 5. Run the ifortvars.bat program with the required architecture argument. > In my case, it was intel64: > > C:\bill>"c:\Program Files (x86)\Intel\ComposerXE-2011\bin\ifortvars.bat" > intel64 > Intel(R) Parallel Studio XE 2011 > Copyright (C) 1985-2010 Intel Corporation. All rights reserved. > Intel(R) Composer XE 2011 Update 1 (package 127) > Setting environment for using Microsoft Visual Studio Shell 2008 x64 tools. > > 6. Now run the "set" command again to write a file containing the system > environment variables after configuration by ifortvars.bat: > > C:\bill>set >afterConfig.txt > > 7. Compare the two files, beforeConfig.txt and afterConfig.txt, to > determine the difference in system environment variable before and after > configuration with ifortvars.bat. In my case, there were over two dozen new > variables in the afterConfig.txt associated with Composer XE 2011 and Visual > Studio. Fortunately, as with previous Intel versions, there are only three > critical variables to change for the compiler: PATH, LIB and INCLUDE. > > 8. To access the system environment variables on Windows 7, right click on > the Computer icon on your desktop, click Properties, select Advanced system > settings, and then finally the "Environment Variables ..." button. In my > case, I had to add two new variables LIB and INCLUDE and modify the PATH > variable. In all three cases, I used the values found in the > afterConfig.txt file after the = sign as the variable value for the LIB, > INCLUDE and PATH variables, respectively. The values you find may be > slightly different. > > LIB=c:\Program Files (x86)\Intel\ComposerXE-2011\compiler\lib;c:\Program > Files (x86)\Intel\ComposerXE-2011\compiler\lib\intel64;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\VC\lib\amd64;C:\Program Files > (x86)\Microsoft Visual Studio > > INCLUDE=c:\Program Files > (x86)\Intel\ComposerXE-2011\compiler\include;c:\Program Files > (x86)\Intel\ComposerXE-2011\compiler\include\intel64;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\VC\atlmfc\include;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\VC\include;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\VC\PlatformSDK\include;c:\Program Files > (x86)\Intel\ComposerXE-2011\mkl\include; > > Path=c:\Program Files (x86)\Intel\ComposerXE-2011\bin\intel64;c:\Program > Files (x86)\Intel\ComposerXE-2011\redist\intel64\compiler;c:\Program Files > (x86)\Intel\ComposerXE-2011\redist\intel64\mpirt;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\Common7\IDE;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\VC\BIN\x86_amd64;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\Common7\Tools;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\Common7\Tools\bin;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\\VC\PlatformSDK\bin;c:\Program Files > (x86)\Intel\ComposerXE-2011\redist\intel64\mkl;c:\Program Files > (x86)\Intel\ComposerXE-2011\redist\intel64\compiler;C:\Program Files > (x86)\Intel\ComposerXE-2011\redist\intel64\mkl;C:\Program Files > (x86)\Intel\ComposerXE-2011\redist\ia32\mkl;C:\Program Files > (x86)\Intel\ComposerXE-2011\redist\intel64\mpirt;C:\Program Files > (x86)\Intel\ComposerXE-2011\redist\intel64\compiler;C:\Program Files > (x86)\Intel\ComposerXE-2011\redist\ia32\mpirt;C:\Program Files > (x86)\Intel\ComposerXE-2011\redist\ia32\compiler;C:\Program Files > (x86)\Intel\ComposerXE-2011\compiler\lib;C:\Program Files\Common > Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common > Files\Microsoft Shared\Windows Live;C:\Program Files > (x86)\Intel\Compiler\11.1\060\lib\Intel64;C:\Program Files > (x86)\Intel\Compiler\11.1\060\lib\ia32;C:\Program Files (x86)\Common > Files\Microsoft Shared\VSA\9.0\VsaEnv;C:\Program Files > (x86)\Intel\Compiler\11.1\060\mkl\em64t\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program > Files\Broadcom\Broadcom 802.11\Driver;C:\Program Files > (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Windows > Live\Shared;C:\Program Files > (x86)\gfortran\libexec\gcc\i586-pc-mingw32\4.5.0;C:\Program Files > (x86)\gfortran\bin > > Use caution, particularly when setting the PATH variable, as there is a > 2047 character limit. Be sure to save the new variables/values. > > 9. Close the DOS window (if still open) and then open a new DOS window. > Copy the gmtest.for file supplied with NONMEM and PDx-Pop to your working > directory to test the compiler and run the resulting compiled program: > > C:\bill>ifort gmtest.for > Intel(R) Visual Fortran Intel(R) 64 Compiler XE for applications running on > Intel(R) 64, Version 12.0.1.127 Build 20101116 > > Copyright (C) 1985-2010 Intel Corporation. All rights reserved. > > Microsoft (R) Incremental Linker Version 9.00.21022.08 > Copyright (C) Microsoft Corporation. All rights reserved. > > -out:gmtest.exe > -subsystem:console > gmtest.obj > > gmtest.obj > > C:\bill>gmtest.exe > ICON Development Solutions - Tools for Expediting > Population Analysis (c) 2009 > > Note: gmtest.for is only a minimal test and may not guarantee the compiler > is completely configured. Installation of NONMEM will provide the > definitive test of the compiler. > William J. Bachman, Ph.D. > Director, Pharmacometrics R&D > Icon Development Solutions > 6031 University Blvd., Suite 300 > Ellicott City, MD 21043 > Office 215-616-8699 > [email protected] > > > >