[CMake] Problems with Intel Fortran 11 on Windows XP

Tue Jun 2 20:55:13 EDT 2009

Bill,
I forgot to provide details for the build case that fails when using IVF 11
with the Visual Studio 9 2008 Generator.  Assuming that I have a hacked
version of CMake that produces .vfproj files with Version="11.0", the
following project will generate a .sln (and .vfproj) file, but the project
fails to generate the requested library:

[ftest.f]
        subroutine foo
           print *, "hello"
        end subroutine

[CMakeLists.txt]
cmake_minimum_required(VERSION 2.6)
project(FortranTestFLib)
enable_language( Fortran )
set(CMAKE_VERBOSE_MAKEFILE ON)
add_library(flib ftest.f)
set_target_properties( flib PROPERTIES LINKER_LANGUAGE Fortran )

Thanks,

-kt

On Tue, Jun 2, 2009 at 5:32 PM, Kelly (KT) Thompson <kt at transpireinc.com>wrote:

> Bill,
> Thanks for offering to look into this problem with Intel Visual Fortran
> integrated into Visual Studio.  We are trying to patch up our CMake files so
> that we can build using the Visual Studio IDE (NMake Makefiles work fine)
> and have run into this where Intel Visual Fortran 11.0 (full version, 32 and
> 64-bit environments) refuses to work.  I tried hacking the CMake source code
> to put "11.0" into the vfproj files (as suggested by
> Tormod.Ravnanger.Landet at dnv.com), but that didn't solve all of our issues.
>   Anyway,...
>
> I decided to look around to see if I could come up with something useful
> for detecting which IVF is integrated with Visual Studio.  I found some
> potentially useful information in HKCU (shown below).  You will notice that
> there is a key for each IVF that has been integrated with Visual Studio.  In
> my case, I see versions 10.1.025, 11.0.039 and 11.0.074.  However, when I
> run Visual Studio, I can only access the newest version of ifort (I even
> tried running devenv /useenv from my IVF 10.1 command prompt but ended up
> with 11.0.074 inside of visual studio).  Also, each key has several values
> that I have removed from the output below.  I provided a sampling from the
> last key.
>
> Another indicator of IVF's version are the environment variables that are
> set by Intel's installer.  I have the following:
>
> IFORT_COMPILER10=C:\Program Files (x86)\Intel\Compiler\Fortran\10.1.025
> IFORT_COMPILER11=C:\Program Files (x86)\Intel\Compiler\11.0\074\fortran\
>
> It would be great to see IVF 11 support with Visual Studio Generators.
>  Thanks for taking a look!
>
> -kt
>
> ======================================================================
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel Fortran]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\101]
> "ExtFree"=".f90;.F95"
> "ExtFixed"=".f;.for;.fpp"
> "HeadersFree"=""
> "HeadersFixed"=".fi;.fd"
> "LogBuilds"=dword:00000001
> "ContinueOnErrors"=dword:00000000
> "ShowEnvInLog"=dword:00000000
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\101\101.025]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\101\101.025\IA32_EM64T]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\101\101.025\IA32_IA32]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\101\SelectedCompilers]
> "IA32"="101.025|IA32_IA32"
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\110]
> "ExtFree"=".f90;.F95"
> "ExtFixed"=".for;.fpp"
> "HeadersFree"=""
> "HeadersFixed"=".fi;.fd"
> "LogBuilds"=dword:00000001
> "ContinueOnErrors"=dword:00000000
> "ShowEnvInLog"=dword:00000000
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\110\110.039]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\110\110.039\EM64T_EM64T]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\110\110.039\IA32_IA32]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\110\110.074]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\110\110.074\EM64T_EM64T]
>
> [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Intel
> Fortran\VFToolOpt\110\110.074\IA32_IA32]
> "BinDir"="$(IFortInstallDir)bin\\ia32;$(CommonProgramFiles)\\Intel\\Shared
> Files\\Ia32\\Bin;$(VSInstallDir)Common7\\IDE;$(VCInstallDir)BIN;$(VSInstallDir)Common7\\Tools;$(VSInstallDir)Common7\\Tools\\bin;$(FrameworkDir)$(FrameworkVersion);$(WindowsSdkDir)bin;$(PATH)"
>
> "LibDir"="$(IFortInstallDir)lib\\ia32;$(VCInstallDir)atlmfc\\lib;$(VCInstallDir)lib;$(WindowsSdkDir)lib;"
>
> "IncludeDir"="$(IFortInstallDir)include;$(IFortInstallDir)include\\ia32;$(VCInstallDir)atlmfc\\include;$(VCInstallDir)include;$(WindowsSdkDir)include;"
> "DefaultOptions"="/Qvc9 /Qlocation,link,\"$(VCInstallDir)bin\""
>
> ======================================================================
>
> On Thu, Dec 18, 2008 at 5:16 AM, Bill Hoffman <bill.hoffman at kitware.com>wrote:
>
>> Tormod.Ravnanger.Landet at dnv.com wrote:
>>
>>  -------------------
>>> Intel(R) Visual Fortran Compiler Professional for applications running
>>> on IA-32, Version 11.0    Build 20081105 Package ID: w_cprof_p_11.0.066
>>> Copyright (C) 1985-2008 Intel Corporation.  All rights reserved.
>>> 30 DAY EVALUATION LICENSE
>>>
>>> ifort: NOTE: The evaluation period for this product ends on 9-jan-2009
>>> UTC.
>>> ifort: command line error: no files specified; for help type "ifort
>>> /help"
>>> -------------------
>>>
>>> Everything up to and including "w_cprof_p_11.0.066" is on one line
>>>
>>>  I guess what really matters is which version of ifort is integrated by
>> default into the visual studio IDE.  There must be some way to figure that
>> out...
>>
>> -Bill
>>
>> _______________________________________________
>> CMake mailing list
>> CMake at cmake.org
>> http://www.cmake.org/mailman/listinfo/cmake
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20090602/247c4f93/attachment-0001.htm>