I've been reading through the archives and followed instructions therein
and am getting the following error (below)
I've setup the ifort batch environment and all seems fine, but it looks
as though devenv is being called with the wrong command line.
Run Build Command:C:\PROGRA~1\MICROS~1.0\Common7\IDE\devenv.com
CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec
Is there a simple fix?
thanks
JB
D:\cmakebuild\mhd\CMakeFiles\CMakeTmp>cmake -G "Visual Studio 9 2008"
D:/Code/CSCS/run_nuprox_hybrid --debug-trycompile
debug trycompile on
-- Check for working Fortran compiler: C:/Program
Files/Intel/Compiler/11.0/074/fortran/Bin/IA32/ifort.exe
-- Check for working Fortran compiler: C:/Program
Files/Intel/Compiler/11.0/074/fortran/Bin/IA32/ifort.exe -- broken
CMake Error at C:/Program
Files/cmake-2.6.4/share/cmake-2.6/Modules/CMakeTestFortranCompiler.cmake:25
(MESSAGE):
The Fortran compiler "C:/Program
Files/Intel/Compiler/11.0/074/fortran/Bin/IA32/ifort.exe" is not able to
compile a simple test program.
It fails with the following output:
Change Dir: D:/cmakebuild/mhd/CMakeFiles/CMakeTmp/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.30729.1.
Copyright (C) Microsoft Corp. All rights reserved.
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:1 (PROJECT)
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 2.6)
should be added at the top of the file. The version specified may be
lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".
This warning is for project developers. Use -Wno-dev to suppress it.
-- Configuring incomplete, errors occurred!
--
John Biddiscombe, email:biddisco @ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
