Hi, I have a build system that works for Intel compilers (v 10) on Linux. Now I am trying to port it to windows. I am using the newest trial versions of Visual Studio (2009) and the Intel compilers (v. 11). The configuration fails with the attached error message. I assume CMake is having problems calling the new version of ifort as it fails during CMake's own check for a working Fortran compiler.
BTW: thanks for the great Fortran support in the latest versions. It compiles my C/Fortran program without any problems on Linux now without any ugly hacks on my side. It just works. Great! Tormod ------------------- Error message --------------------------------- C:\Temp\build>cmake h:\SourceDir -G "Visual Studio 9 2008" -- Check for working Fortran compiler: ifort -- Check for working Fortran compiler: ifort -- broken CMake Error at C:/Program Files/CMake 2.6/share/cmake-2.6/Modules/CMakeTestFortranCompiler.cmake:25 (MESSAGE): The Fortran compiler "ifort" is not able to compile a simple test program. It fails with the following output: Change Dir: C:/Temp/sesam-build/CMakeFiles/CMakeTmp Run Build Command:C:\PROGRA~1\MICROS~1.0\Common7\IDE\devenv.com CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec Microsoft (R) Visual Studio Version 9.0.21022.8. Copyright (C) Microsoft Corp. All rights reserved. The evaluation period for Visual Studio Trial Edition ends in 90 days. Invalid project Use: devenv [solutionfile | projectfile | anyfile.ext] [switches] The first argument for devenv is usually a solution file or project file. You can also use any other file as the first argument if you want to have the file open automatically in an editor. When you enter a project file, the IDE looks for an .sln file with the same base name as the project file in the parent directory for the project file. If no such .sln file exists, then the IDE looks for a single .sln file that references the project. If no such single .sln file exists, then the IDE creates an unsaved solution with a default .sln file name that has the same base name as the project file. Command line builds: devenv solutionfile.sln /build [ solutionconfig ] [ /project projectnameorfile [ /projectconfig name ] ] Available command line switches: /Build Builds the solution or project with the specified solution configuration. For example "Debug". If multiple platforms are possible, the configuration name must be enclosed in quotes and contain platform name. For example: "Debug|Win32". /Clean Deletes build outputs. /Command Starts the IDE and executes the command. /Deploy Builds and then deploys the specified build configuration. /Edit Opens the specified files in a running instance of this application. If there are no running instances, it will start a new instance with a simplified window layout. /LCID Sets the default language in the IDE for the UI. /Log Logs IDE activity to the specified file for troubleshooting. /NoVSIP Disables the VSIP developer's license key for VSIP testing. /Out Appends the build log to a specified file. /Project Specifies the project to build, clean, or deploy. Must be used with /Build, /Rebuild, /Clean, or /Deploy. /ProjectConfig Overrides the project configuration specified in the solution configuration. For example "Debug". If multiple platforms are possible, the configuration name must be enclosed in quotes and contain platform name. For example: "Debug|Win32". Must be used with /Project. /Rebuild Cleans and then builds the solution or project with the specified configuration. /ResetAddin Removes commands and command UI associated with the specified Add-in. /ResetSettings Restores the IDE's default settings, optionally resets to the specified VSSettings file. /ResetSkipPkgs Clears all SkipLoading tags added to VSPackages. /Run Compiles and runs the specified solution. /RunExit Compiles and runs the specified solution then closes the IDE. /SafeMode Launches the IDE in safe mode loading minimal windows. /Upgrade Upgrades the project or the solution and all projects in it. A backup of these files will be created as appropriate. Please see Help on 'Visual Studio Conversion Wizard' for more information on the backup process. Product-specific switches: /debugexe Open the specified executable to be debugged. The remainder of the command line is passed to this executable as its arguments. /useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables instead of IDE paths for VC++ builds. To attach the debugger from the command line, use: VsJITDebugger.exe -p <pid> CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:4 (project) -- Configuring incomplete, errors occurred! Med vennlig hilsen / Best regards, for Det Norske Veritas AS Tormod R. Landet _____________________________ Engineer Ship Hydrodynamics (MTPNO362) Maritime Technical Consultancy Phone: +47 6757 8980 Fax: +47 6757 9911 Web: Maritime Technical Consultancy <http://www.dnv.com/industry/maritime/servicessolutions/consulting/techn icalconsulting/index.asp> **************************************************************************************The contents of this e-mail message and any attachments are confidential and are intended solely for the addressee. If you have received this transmission in error, please immediately notify the sender by return e-mail and delete this message and its attachments. Any unauthorized use, copying or dissemination of this transmission is prohibited. Neither the confidentiality nor the integrity of this message can be vouched for following transmission on the Internet.************************************************************************************** _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake