Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Alan W. Irwin
On 2010-04-04 21:28-0400 John Drescher wrote: On Sun, Apr 4, 2010 at 7:16 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote: Clint (with an old version of MinGW) and I (with MinGW-4.5) have been running into a peculiar CXX error for MinGW/MSYS on Wine. Enabling C++ _sometimes_ fails because

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Alan W. Irwin
On 2010-04-05 00:40-0700 Alan W. Irwin wrote: On 2010-04-04 21:28-0400 John Drescher wrote: [...] I believe the issue is caused by wine pulling in at least some of environment variables from the linux system. That idea of something leaking through from Linux to Wine to disrupt CMake might

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Bill Hoffman
Alan W. Irwin wrote: On 2010-04-05 00:40-0700 Alan W. Irwin wrote: On 2010-04-04 21:28-0400 John Drescher wrote: [...] I believe the issue is caused by wine pulling in at least some of environment variables from the linux system. That idea of something leaking through from Linux to Wine

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Alan W. Irwin
On 2010-04-05 11:31-0400 Bill Hoffman wrote: Alan W. Irwin wrote: On 2010-04-05 00:40-0700 Alan W. Irwin wrote: On 2010-04-04 21:28-0400 John Drescher wrote: [...] I believe the issue is caused by wine pulling in at least some of environment variables from the linux system. That idea of

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Clinton Stimpson
On Apr 5, 2010, at 11:50 AM, Bill Hoffman wrote: Alan W. Irwin wrote: Have you run cmake --trace yet to figure out what is including what and where? Yes, as alluded to above the complete result for cmake --trace --debug-output for a CMakeLists.txt file consisting of just project(test

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Alan W. Irwin
On 2010-04-05 13:50-0400 Bill Hoffman wrote: Alan W. Irwin wrote: Have you run cmake --trace yet to figure out what is including what and where? Yes, as alluded to above the complete result for cmake --trace --debug-output for a CMakeLists.txt file consisting of just project(test NONE)

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Bill Hoffman
Clinton Stimpson wrote: So interleaving wine tracing and cmake tracing along with some debugging... the problem comes from within SystemTools::GetActualCaseForPath() where it takes as input somepath/CMakeTestCXXCompiler.cmake and returns somepath/CMakeFortranInformation.cmake. I'm guessing

[CMake] use of ${cmake_command}

2010-04-05 Thread AKHRES Nader
Hello, I've seen some examples where ${CMAKE_COMMAND} is used instead of cmake, typically in post build command Is it a better practice for portability? Nad ___ Powered by www.kitware.com Visit other Kitware open-source projects at

[CMake] cmake+build machine

2010-04-05 Thread AKHRES Nader
Hello, does someone use a nightly build engine like CruiseControl with CMake? Does it make sense? Nad ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Alan W. Irwin
On 2010-04-05 13:04-0600 Clinton Stimpson wrote: On Apr 5, 2010, at 11:50 AM, Bill Hoffman wrote: Alan W. Irwin wrote: Have you run cmake --trace yet to figure out what is including what and where? Yes, as alluded to above the complete result for cmake --trace --debug-output for a

Re: [CMake] debug with codeblocks project

2010-04-05 Thread AKHRES Nader
thanks, it works now. Le 04/04/2010 20:51, Ryan Pavlik a écrit : Yes, the CodeBlocks generator in CMake is just an extension of the makefile one (note that it's named Code::Blocks - Unix Makefiles) so the same thing applies: set CMAKE_BUILD_TYPE as desired. In general, when using a

Re: [CMake] cmake+build machine

2010-04-05 Thread Ryan Pavlik
On 4/5/10 4:01 PM, AKHRES Nader wrote: Hello, does someone use a nightly build engine like CruiseControl with CMake? Does it make sense? Nad It depends on what you're doing and who you interoperate with, but the suite of CMake/CTest and CDash provide a good nightly, continuous, and

Re: [CMake] use of ${cmake_command}

2010-04-05 Thread Eric Noulard
2010/4/5 AKHRES Nader nader.akh...@laposte.net: Hello, I've seen some examples where ${CMAKE_COMMAND} is used instead of cmake, typically in post build command Is it a better practice for portability? Yes. This way you can be sure to use the very same 'cmake' that you used to

Re: [CMake] use of ${cmake_command}

2010-04-05 Thread Ryan Pavlik
Yes, since the cmake that is in the user's PATH might not be the cmake they are using/want to use. Generally, avoid hardcoding application/executable names or locations. Ryan On 4/5/10 4:00 PM, AKHRES Nader wrote: Hello, I've seen some examples where ${CMAKE_COMMAND} is used instead of

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Clinton Stimpson
On Apr 5, 2010, at 2:19 PM, Bill Hoffman wrote: Clinton Stimpson wrote: So interleaving wine tracing and cmake tracing along with some debugging... the problem comes from within SystemTools::GetActualCaseForPath() where it takes as input somepath/CMakeTestCXXCompiler.cmake and returns

Re: [CMake] CXX incorrectly includes CMakeFortranInformation.cmake for MinGW/MSYS/Wine

2010-04-05 Thread Clinton Stimpson
On 04/05/2010 03:00 PM, Alan W. Irwin wrote: On 2010-04-05 13:04-0600 Clinton Stimpson wrote: On Apr 5, 2010, at 11:50 AM, Bill Hoffman wrote: Alan W. Irwin wrote: Have you run cmake --trace yet to figure out what is including what and where? Yes, as alluded to above the complete result