On 3/8/2011 6:41 AM, Biddiscombe, John A. wrote:
Using devenv.com, we're making progress - but the binary produced by
CMakeDetermineCompilerABI is in debug/bin and it's not looking there
- does the devenv do it differently from msbuild?
JB
C:\cmakebuild\fortrantest>C:\cmakebuild\cmake\bin\Debug\cmake.exe
c:\Code\fortrantest -G "Visual Studio 10 Win64" --debug-trycompile
--debug -output debug trycompile on Running with debug output on. --
Check for working Fortran compiler using: Visual Studio 10 Win64
Called from: [2]
C:/Code/cmake/Modules/CMakeTestFortranCompiler.cmake [1]
c:/Code/fortrantest/CMakeLists.txt -- Check for working Fortran
compiler using: Visual Studio 10 Win64 -- works Called from: [2]
C:/Code/cmake/Modules/CMakeTestFortranCompiler.cmake [1]
c:/Code/fortrantest/CMakeLists.txt -- Detecting Fortran compiler ABI
info Called from: [2]
C:/Code/cmake/Modules/CMakeTestFortranCompiler.cmake [1]
c:/Code/fortrantest/CMakeLists.txt CMake Error at
C:/Code/cmake/Modules/CMakeDetermineCompilerABI.cmake:31
(TRY_COMPILE): Cannot copy output executable
''
to destination specified by COPY_FILE:
'C:/cmakebuild/fortrantest/CMakeFiles/CMakeDetermineCompilerABI_Fortran.bin'
Unable to find the executable at any of:
C:/cmakebuild/fortrantest/CMakeFiles/CMakeTmp/cmTryCompileExec.exe
C:/cmakebuild/fortrantest/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe
C:/cmakebuild/fortrantest/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe
Call Stack (most recent call first):
C:/Code/cmake/Modules/CMakeTestFortranCompiler.cmake:59
(CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:2 (project)
Where exactly is cmTryCompileExec.exe after the command is run?
_______________________________________________
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
