Re: [CMake] cmake + OSX + gfortran + 64bit problem

Okay, thanks, I'll have a look. But isn't this also CMake bug? In most other cases it seems to do a good job of knowing which flags to use for different compilers. -Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of j s Sent: Thursday,

[CMake] cmake + OSX + gfortran + 64bit problem

Here's what I've got: Cmake: 2.8.3 OS X: 10.5.x gfortran: 4.5.1 I'm trying to build a Fortran program on OS X using CMake. I'm trying to write CMakeLists.txt files that can handle either the GNU fortran compiler or the Intel fortran compiler. When set CMAKE_OSX_ARCHITECTURES to x86_64, the

Re: [CMake] cmake + OSX + gfortran + 64bit problem

Thanks, but a guy on the gfortran mailing list makes it sound like they have no intention to support -arch x86_64 on the Mac. I need to find a solution that will work on stock versions of gfortran, unfortunately. That probably depends which gfortran you are using on the Mac. I've used the

[CMake] Best way to sniff for Fortran compiler?

Any suggest for the most-proper way, in a CMakeLists.txt file, to determine whether the Intel vs. GNU fortran compiler will be used? I need to use different sets of source files, and different compiler flags, depending on that detail. Christian Convey Scientist, NUWC Division Newport 1176

Re: [CMake] Creating CMakeLists files from Solutions, Projects and Makefiles

Funny timing - I just did that today, at least in a crude manner. Long story short: On Unix/Linux/Mac, you can use the command-line tools (grep, sed, cut, xargs, etc.) to get the list of all source file that comprise the solutions' projects. If your needs aren't too fancy, it's pretty trivial

[CMake] CTest support for Coverity Prevent?

I've got a license for Coverity Prevent (a pretty decent static analysis tool). Although Prevent has a web interface, I was thinking that it would also be nice to run Prevent on a nightly basis and have the results appear on the same dashboard populated by my nightly ctest runs. Has anyone

Re: [CMake] An observation about CTest

I don't expect a lot of support for what I'm about to say, but I think it's perhaps worth saying anyway... It seems like CMake's and CTest's have outgrown their scripting languages. As far as I can tell, all CMake/CTest variables are either macro formal parameters, or variables in a single

Re: [CMake] An observation about CTest

To: Convey, Christian J CIV NUWC NWPT Cc: alokgo...@hotmail.com; cmake@cmake.org Subject: Re: [CMake] An observation about CTest 2010/6/27 Convey, Christian J CIV NUWC NWPT christian.con...@navy.mil: I don't expect a lot of support for what I'm about to say, but I think it's perhaps worth

Re: [CMake] An observation about CTest

. Irwin [mailto:ir...@beluga.phys.uvic.ca] Sent: Sunday, June 27, 2010 16:49 To: Convey, Christian J CIV NUWC NWPT Cc: alokgo...@hotmail.com; cmake@cmake.org Subject: Re: [CMake] An observation about CTest Your remarks focus on old-fashioned macros so it is possible you are not aware

[CMake] How specify revision for ctest_update(...) do check out?

I'm writing a (new style) ctest script. When I run it, I want it to check out the project's source code, as it was at the very beginning of the day (00:00). What's the right way to do this? (BTW, I'm using Subversion.) I would have assumed it's done by setting CTEST_NIGHTLY_START_TIME, but

[CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND

Could someone explain something to me about CTest's conventions? I'm reading throught this page: http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE It sounds like the variable CTEST_CHECKOUT_COMMAND is meant to contain the ensure checkout command, including all arguments.

Re: [CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND

I'm reading throught this page: http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE It sounds like the variable CTEST_CHECKOUT_COMMAND is meant to contain the ensure checkout command, including all arguments. Wow, I'm typing miserably lately. s/ensure/entire smime.p7s

Re: [CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND

the same effect using a SET(CVS_UPDATE_OPTIONS ...) call? - Christian -Original Message- From: Karthik Krishnan [mailto:karthik.krish...@kitware.com] Sent: Thursday, June 24, 2010 11:51 To: Convey, Christian J CIV NUWC NWPT Cc: cmake@cmake.org Subject: Re: [CMake

[CMake] Ways of setting CTEST_BUILD_NAME

Suppose I want do just use ctest in a dead-simple manner: add a few lines to my CMakeLists.txt files, then run cmake . make test. In this scheme, what's the easiest way I can set CTEST_BUILD_NAME? Simply setting that variable in my CMakeLists.txt file doesn't *seem* to be effective. Thanks,

Re: [CMake] Ways of setting CTEST_BUILD_NAME

...@kitware.com] Sent: Thursday, June 24, 2010 15:22 To: Convey, Christian J CIV NUWC NWPT Cc: cmake@cmake.org Subject: Re: [CMake] Ways of setting CTEST_BUILD_NAME cmake -DBUILDNAME=MyBuildName . make make test test does not depend on all so that it can just run quickly... so you need the middle

[CMake] An observation about CTest

Hi guys, First off, I'd like to give my heartfelt thanks to everyone who's helped me figure out how to use CTest in the past few weeks. I'm very grateful to you and to those who develop CTest. I'd like to offer one piece of constructive criticism about ctest. If found learning how to use it

[CMake] How set Build Name in CTest/CDash?

I'm using CTest to submit results to CDash. Can anyone tell me how to specify the text that shows up in CDash's Build Name column? The manpage for ctest says that I can set the CMAKS_SYSTEM and CMAKE_CXX_COMPILER variables, but I'm concerned that doing so may mess up my build. I have a Linux

Re: [CMake] How set Build Name in CTest/CDash?

The new-fashioned way is to set CTEST_BUILD_NAME in your ctest -S script prior to ctest_configure, ctest_build and ctest_submit... set(CTEST_BUILD_NAME myBuildName) Can I also do this in my CMakeLists.txt file? I guess I'm unclear on whether or not there aer some things that can *only* be

[CMake] ctest meant to be re-entrant?

I'm having trouble getting my mind around how CTest is intended to be used. Could someone explain this to me? When you embed ctest-related statements into a CMakeLists.txt file, and then run cmake on that file, you produce a CTestConfig.cmake file. This file is eventually executed by ctest.

Re: [CMake] ctest meant to be re-entrant?

Sorry, that was embarrassing. Pretend I had said, CTestTestFile.cmake instead of CTestConfig.cmake. CTestConfig.cmake should be a source file in your source tree. Nothing should be writing it automatically. On Mon, Jun 21, 2010 at 11:21 AM, Convey, Christian J CIV NUWC NWPT

Re: [CMake] ctest meant to be re-entrant?

Sorry, that was embarrassing. Pretend I had said, CTestTestFile.cmake instead of CTestConfig.cmake. Well, in that case CMake writes the CTestTestFile.cmake files whenever it configures a build tree. (So, from a ctest -S script, during the ctest_configure(...) call.)

Re: [CMake] ctest meant to be re-entrant?

David is right; it's confusing because ctest can be used in several different ways. I think it's actually much worse than he says, because as far as I can tell, ctest can be used in four completely different and mutually incompatible ways, each with their own idiosyncrasies. To make

Re: [CMake] ctest meant to be re-entrant?

But, back to the original subject, if you can re-state what your goal is a little bit, hopefully we can figure out a way to get you there. Thanks very much. It's maybe more than can/should be done using ctest. That is, some shell scripting might be in order as well... I have a CDash

[CMake] Problem getting out-of-source builds (yes I deleted CMakeCache.txt)

Hi guys, Does anyone know why I might be having trouble getting out-of-source builds? I have this directory structure: foo /build /src /CMakeLists.txt /library_A /CMakeLists.txt /a.cpp ... /library_B

Re: [CMake] Problem getting out-of-source builds (yes I deleted CMakeCache.txt)

My goal is to have this work: cd foo/build cmake ../src/CMakeLists.txt that should be: cmake ../src Thanks. That did the trick. smime.p7s Description: S/MIME cryptographic signature ___ Powered by www.kitware.com Visit other Kitware

[CMake] Intel compiler on OS X?

Has anyone successfully used cmake (2.4.6) with the Intel icc compiler (version 11.1) for OS X? When I run cmake I get an error: During cmake's configure phase, cmake tells me that it couldn't successfully compile a simple test program using the icc compiler. The specific error issued is by

Re: [CMake] Intel compiler on OS X? (solved)

It turns out that to compile c++ code, you use the icpc command to invoke the compiler, rather than the icc command. -Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Convey, Christian J CIV NUWC NWPT Sent: Thursday, July 02, 2009 13

[CMake] TARGET_LINK_LIBRARIES for library targets?

I've got three libraries, A, B, C. C uses symbols from B, and B uses symbols from A. When I build these libraries as static libraries (libA.a, libB.a, and libC.a), the linker is perfectly happy to produce libC.a even if I haven't told it about B. It seems that all that matters is, when I'm

[CMake] Understanding why CMAKE_BUILD_TYPE cannot be set

From the mail archives and personal experience, it looks to me like commands of the form: SET(CMAKE_BUILD_TYPE Debug) aren't effective. I don't think I fully understood the explanations of why, though. If it's ok to specify this variable on the cmake command line ( cmake

[CMake] Recoverable build errors?

I've got a top-level CMake project with numerous executable and library sub-projects. I'd like to have CMake generate Makefiles such that if one of those subprojects fails the build process, the Makefile still attempts to build all other subprojects that aren't dependent on any of those which