[cmake-developers] ExternalProject: using the same argument multiple times

Hi Dave, I want to wrap the externalproject_add() function, so that in the normal case only the git URL has to be specified, and all other arguments have been already set. But it should still be possible to override my default arguments. So I had a look how the argument parsing is done in

Re: [cmake-developers] ExternalProject: using the same argument multiple times

It is unexpected (and user/pilot error, if encountered) to have multiple INSTALL_DIR arguments to ExternalProject_Add. Why do you have to override the function in order to achieve your goal? Most ExternalProject arguments have reasonable default values for the corresponding properties, and can

[cmake-developers] I want to use CMake in Solaris10 x86

Hi I cannot find insall packet in download list,only Solaris spack packet can be found.How to solve this question ,thanks 2011-06-14 feng.zhou ___ cmake-developers mailing list cmake-developers@cmake.org

Re: [cmake-developers] I want to use CMake in Solaris10 x86

On 2011-06-14 10:37+0800 feng.zhou wrote: Hi I cannot find insall packet in download list,only Solaris spack packet can be found.How to solve this question ,thanks Try building cmake from the source code using the bootstrap method (i.e. running the bootstrap script in the top-level source

Re: [CMake] installing without building the whole project

On Thursday 09 June 2011, Michael Hertling wrote: On 06/09/2011 03:34 PM, Dominik Szczerba wrote: Hi, I have a big project with several subfolders. In one subfolder's cmake file I have e.g. INSTALL(TARGETS test DESTINATION ${CMAKE_INSTALL_PREFIX} CONFIGURATIONS RELEASE) Now

Re: [CMake] ccmake options organization

On Friday 10 June 2011, Tim Gallagher wrote: Hi all, We have a code that has a lot of options to enable/disable at compile time, and we'd also like to use ccmake to generate input files to run the code (possibly several hundred options combined). But the way the curses gui organizes things

[CMake] CMAKE internal variables, files and scope

I would like to know if there is a list of all variables defined by cmake internally. ie. variables created by the various cmake supplied platform files etc. and internal to the application but not by the various find modules etc. that are explicitly invoked. I would like to know for each

Re: [CMake] ccmake options organization

I agree, I much prefer it too. But the bigger issue for us is that our builds are on remote machines that we cannot X-forward, so the gui isn't even an option. We've been hearing people in our lab say It would be nice if... and so I thought I'd throw it out there to see what others thought

Re: [CMake] ccmake options organization

I would also very much like to see some form of grouping to be possible in ccmake. Right now, the only way to avoid clutter is to mark the large majority of the variables as advanced and keep only the ones that would be used frequently used and this is still just a half-baked solution. One neat

[CMake] (no subject)

Hello I have the following stupid problem with cmake: I want CMAKE_BUILD_TOOL or the deprecated CMAKE_MAKE_PROGRAM to be set to /usr/bin/make -j12    (for multithreaded build) how can we pass arguments to the build tool (make)? in eclipse that does not work because in the

Re: [CMake] ccmake options organization

On 6/13/2011 11:02 AM, Szilárd Páll wrote: I would also very much like to see some form of grouping to be possible in ccmake. Right now, the only way to avoid clutter is to mark the large majority of the variables as advanced and keep only the ones that would be used frequently used and this is

Re: [CMake] (no subject)

On Monday 13 June 2011, Gabriel Nützi wrote: Hello I have the following stupid problem with cmake: I want CMAKE_BUILD_TOOL or the deprecated CMAKE_MAKE_PROGRAM to be set to /usr/bin/make -j12(for multithreaded build) how can we pass arguments to the build tool (make)? in

[CMake] Dealing with down servers when using FindSubversion.cmake

I use code like the following to append a version to my applications based on the current svn rev. FIND_PACKAGE(Subversion) IF(Subversion_FOUND) Subversion_WC_INFO(${PROJECT_SOURCE_DIR} Project) MESSAGE(Current revision is ${Project_WC_REVISION})

[CMake] Link flags not applied to static library

Hello all, I'm using CMake 2.8.4 and am seeing an odd differenc between static and shared libraries in regard to the LINK_FLAGS property. In particular, I'm enabling Whole program optimization in Visual Studio 2010, which is done by add /GL as a compiler flag and /LTCG as a linker flag for the

Re: [CMake] Determine Installer Build Configuration in Visual Studio

On Fri, Jun 10, 2011 at 11:02 AM, Jason Gochanour jrgoc...@lanl.gov wrote: I think you may be right. CMAKE_INSTALL_CONFIG_NAME doesn't contain a value when I run a fresh build of the PACKAGE project in Visual Studio. If it isn't possible to tell CPack what build configuration the user chooses

Re: [CMake] Dealing with down servers when using FindSubversion.cmake

Am Montag, 13. Juni 2011, 13:02:34 schrieb John Drescher: I use code like the following to append a version to my applications based on the current svn rev. FIND_PACKAGE(Subversion) IF(Subversion_FOUND) Subversion_WC_INFO(${PROJECT_SOURCE_DIR} Project) MESSAGE(Current revision

Re: [CMake] Dealing with down servers when using FindSubversion.cmake

On Mon, Jun 13, 2011 at 3:16 PM, Rolf Eike Beer e...@sf-mail.de wrote: Am Montag, 13. Juni 2011, 13:02:34 schrieb John Drescher: I use code like the following to append a version to my applications based on the current svn rev. FIND_PACKAGE(Subversion) IF(Subversion_FOUND)      

[CMake] install python module

Hi, I am creating my python modules like: VTK_WRAP_PYTHON3 (vtkmyFilteringPython FilteringPython_SRCS ${SOURCES}) ADD_LIBRARY (vtkmyFilteringPythonD ${FilteringPython_SRCS}) TARGET_LINK_LIBRARIES(vtkmyFilteringPythonD vtkmyFiltering vtkFilteringPythonD vtkImagingPythonD

Re: [CMake] include_directories(SYSTEM, GNU.cmake and -isystem for C (not CXX)

On 06/11/2011 02:08 AM, Campbell Barton wrote: To follow up on this, I tested this on a test project and found the problem was in my own macro which wasn't initializing an include list. So only the set(CMAKE_INCLUDE_SYSTEM_FLAG_C -isystem ) remains which should be fixed in CMake but is easy

[CMake] Errors using CMAKE for cross compiling.

Try cross compiling using CMAKE, target tool chain is ARM RVCT4, got errors on both Windows and Ubuntu. Please help, thanks in advance. 1. On Ubuntu. ADD_EXECUTABLE(hello main.c) Fatal error: C3900U: Unrecognized option '-rdynamic'. ADD_EXECUTABLE(hello SHARED main.c) Fatal error:

Re: [CMake] Errors using CMAKE for cross compiling.

On Tuesday 14 Jun 2011 9:46:56 AM jianhua wrote: Try cross compiling using CMAKE, target tool chain is ARM RVCT4, got errors on both Windows and Ubuntu. Please help, thanks in advance. 1. On Ubuntu. ADD_EXECUTABLE(hello main.c) Fatal error: C3900U: Unrecognized option '-rdynamic'.

[Cmake-commits] CMake branch, next, updated. v2.8.4-1733-g412fbe5

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 412fbe5892aa00eea675a464130c75b20d2765a5 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.4-1735-gadf9c1e

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 adf9c1e330975d8611b406d1611b086cb0e4f564 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.4-1737-gcdab855

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 cdab85513cc99e396d0f5ea2aff8834170fab1e4 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.4-1739-gcd41daa

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 cd41daa4457439d282bb59f216d1bcf0dc744ef0 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.4-1741-g4b204f7

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 4b204f779172439f8bb2224ee473a449a9e96058 (commit) via