[cmake-developers] Flag ordering

Can anyone tell me why the default CMAKE*_FLAGS_*_INIT values get placed *after* the specified CFLAGS? This makes it hard to override the -O value specified there. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX:

Re: [cmake-developers] Flag ordering

On 04/18/2013 11:24 AM, Orion Poplawski wrote: Can anyone tell me why the default CMAKE*_FLAGS_*_INIT values get placed *after* the specified CFLAGS? This makes it hard to override the -O value specified there. Per-config flags are more specific than general flags. Options like -O are

[cmake-developers] RFC: pretty/HTML output in test logs in ctest/cdash

Hi, attached are two patches for ctest and cdash from Volkan (on CC). They are not ready for inclusion, but before we continue to work in this, we'd like to get some comments whether this is a good idea, the right approach, etc. So, here we go. We are using cdash a lot, and for many of our

Re: [CMake] Superbuild subprojects and find_package()

Hi John, the primary tool for superbuilds in CMake's arsenal is ExternalProject_Add from module ExternalProject. I don't have much experience with it, but you can read its docs to see if it could help you. Petr On Thu, Apr 18, 2013 at 5:38 AM, John Gallagher johnkgallagher+cm...@gmail.com

Re: [CMake] Superbuild subprojects and find_package()

Hi, On Thu, Apr 18, 2013 at 5:38 AM, John Gallagher johnkgallagher+cm...@gmail.com wrote: Hello all, Some Googling has led me to questions that have been asked that are similar to this one but I haven't seen a definitive answer. I'm trying to set up a CMake superbuild where there are

[CMake] The source directory

Hi. I'm trying to build a build with cmake-2.8.10.2-linux for 'gromacs-4.6.1' as the build target. First, I extracted gromacs-4.6.1.tar.gz and, create a new folder; build inside the extracted folder. Then, inside build folder, I configured using CMake. $ tar -xvzf gromacs-4.6.1.tar.gz $ cd

Re: [CMake] Superbuild subprojects and find_package()

Hello John, Maybe I am missing something but can't you do something like this in proj2s cmakelists.txt? if( TARGET proj1 ) list_of_libraries_to_link_against( ${ list_of_libraries_to_link_against} proj1 ) else( TARGET proj1 ) find( proj1 required ) list_of_libraries_to_link_against( ${

Re: [CMake] Superbuild subprojects and find_package()

Hello John, On Wednesday 17 April 2013 23:38:36 John Gallagher wrote: 3. (This one is unclear.) Somehow build proj1 before configuring proj2, and point proj2 at proj1's build directory so it can find Proj1Config.cmake. This seems fragile at best (prefix, RPATH, etc issues). when using

[CMake] Copy dlls to release and debug folder

Hi, I was successful in creating and building a project using CMake on Windows (Visual Studio). After the build when I try to run the application it throws an error asking for the dlls of Qt (I know it is a common case in Windows, usually we do copy the dlls to debug/release folder where the exe

Re: [CMake] The source directory

Hi, On Thursday, 18. April 2013, 09:02:13, 中野佑香 wrote: $ tar -xvzf gromacs-4.6.1.tar.gz $ cd gromacs-4.6.1 $ mkdir build $ cd build $ cmake .. However, I got an error. --- CMake Error: The source directory

Re: [CMake] Copy dlls to release and debug folder

Hi Lloyd, Personally I copy the DLLs to the VS folder (so that the program can be run from visual studio) using the following script. It looks more complicated than it is. A macro is available to several of my projects to select which Qt module they use and create a list of dlls to copy. Then

Re: [CMake] Copy dlls to release and debug folder

I assume that this is the recommended approach. I tried to use the script you have provided, the call GetQtDLLs(DEBUG_DLLS RELEASE_DLLS) is not populating any of the variables (DEBUG_DLLS or RELEASE_DLLS) with qt dll names. I am new to cmake, Am I missing something? Thanks, Lloyd On Thu,

[CMake] CMake/CTest/CDash Training Course (Lyon, France)

Kitware will be holding a developers training course on May 27, 2013 in Lyon, France. This one-day course will cover CMake, CTest, CPack and CDash Please visit our website for more information and registration details (early registration ends May 6) at:

Re: [CMake] Copy dlls to release and debug folder

Normally when you find the Qt4 package it selects some defaults libraries (and the QT_USE_FILE). But you have to specify some extra modules you may need before including the QT_USE_FILE. The QT_USE_FILE defines the dependencies and includes the folders you need. For example I have:

Re: [CMake] Superbuild subprojects and find_package()

Hello John, I made some generic scripts to answer has those kind of problem. There is an example in the folder Examples/FrameworkTest. You can find the scripts on GitHub: https://github.com/Athius/FrameworkCMakeToolkit I hope this is helpful. Best regards, Romain Le 18/04/13 05:38, John

[CMake] Building cmake: ccmake not built

Hi all; I'm tring to build cmake using a cross-compiler environment so cmake itself will run on a different platform. It's working well, except that ccmake is not getting compiled (neither is cmake-gui but that's OK). I do have curses libraries installed and other curses programs are built and

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2798-gdb303a4

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via db303a426c29011d766496b004766f3d9e6f5f3a (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2800-gf6b2462

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via f6b24625389d80acb6c55b294b9d56bc652c5892 (commit) via

[Cmake-commits] CMake branch, release, updated. v2.8.10.2-1003-g573f39c

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, release has been updated via 573f39cb2ad6dcf70f85514132a504e9c2da1e0b (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2807-ged86e1a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via ed86e1ad349626d9e71af0ced368df6361bab2cc (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2809-g0eec6e7

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 0eec6e7eddd33651a96c3d6aa708f7e8ca4e566e (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2811-gf988603

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via f988603bc6f15b9c9553653135b691343f5647c1 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-999-ge6c3595

Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 1ea731c..5e01b6d 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -2,5 +2,5 @@ set(CMake_VERSION_MAJOR 2) set(CMake_VERSION_MINOR 8) set(CMake_VERSION_PATCH 10) -set(CMake_VERSION_TWEAK 20130418