Re: [CMake] Parallel make & custom command

Hi Bill: Thanks for your response. More comments below. On 2011-06-30 22:03-0400 Bill Hoffman wrote: On 6/30/2011 5:23 PM, Alan W. Irwin wrote: To help with the general difficulty of getting dependencies right, would it be possible to implement a CMake change so that for a given flag (say --

Re: [CMake] Makefiles without reference to CMake?

This has been discussed a gazillion times, and the answer will always be the same: no. It's impossible. A build tree always depends on CMake, and is not relocatable. Live with it. If your users don't want to use CMake, provide them with a convenience script that does the hard work for them. HT

[CMake] Install targets

Hi, We have a project that has a main executable and dozens of utility executables that may or may not be needed. We can add an executable for each util with EXCLUDE_FROM_ALL defined so just typing make only does the main code and something like 'make grid' compiles the grid generator. But, h

[CMake] Makefiles without reference to CMake?

Hello, I used cmake to build a project and it runs fine on my Linux box as part of a bigger app. But I need to be able to check in the Makefiles along with my code, so that other users don't need to perform the cmake configuration all over. The problem is that the Makefiles generated by cmake h

Re: [CMake] CMake Wiki spammed

Those users have been blocked from our wiki. Let us know if you see any more suspicious activity. Thanks, David On Thu, Jun 30, 2011 at 7:30 PM, David Cole wrote: > I have forwarded this to our IT team... Hopefully it's not too hard to > recover from for them. > > Thanks, > David > > > > On T

Re: [CMake] External_Project_Add() and custom build configurations ?

On Fri, Jul 1, 2011 at 7:23 AM, Glenn Coombs wrote: > I have just started using some externally supplied cmake projects in my > cmake project. To do this I added these lines to my top level > CMakeLists.txt file: > > include(ExternalProject) > > ExternalProject_Add(external_proj > PREFIX

Re: [CMake] CPack -- adding license to files

Sounds like more of a job for perl, python or ruby to me. On Fri, Jul 1, 2011 at 12:17 PM, Raymond Wan wrote: > Hi all, > > I was wondering if there is an easy/automated way that I can get CMake > or CPack to add a license to every source file prior to distribution > of the source. Of course,

[CMake] CPack -- adding license to files

Hi all, I was wondering if there is an easy/automated way that I can get CMake or CPack to add a license to every source file prior to distribution of the source. Of course, I mean that I would provide the wording of the license and "all" it does is copy this license to the top of each source fil

[CMake] install( TARGETS module ...)

Dear all, I am trying to change the default behavior of cmake which installs MODULE to the LIBRARY destination. For example: ... add_library(test MODULE test.c) install(TARGETS test RUNTIME DESTINATION bin LIBRARY DESTINATION lib ARCHIVE DESTINATION lib/static ) ... Will install test

Re: [CMake] Download and Build external dependencies

Looking at the following file may be helpful .. SuperBuild/External_CLAPACK.cmake There are also other examples in the Superbuildfolder. H

Re: [CMake] Download and Build external dependencies

On 07/01/2011 01:48 PM, Martin Köhler wrote: > Hi, > I'm currently trying to write a cmake script, which downloads some > source code and compile it during the configuration step. In my case > this I want to try it with BLAS from netlib.org because it represents > the problem in a good way ( and I

[CMake] Download and Build external dependencies

Hi, I'm currently trying to write a cmake script, which downloads some source code and compile it during the configuration step. In my case this I want to try it with BLAS from netlib.org because it represents the problem in a good way ( and I need it for BLAS and similar structured source code).

Re: [CMake] One source file, different arch

Something like this should do the trick: add_exectuable(myExe32 A.c B.c C.c) add_exectuable(myExe64 A.c B.c D.c) set_target_properties(myExe32 PROPERTIES COMPILE_FLAGS -m32) set_target_properties(myExe32 PROPERTIES LINK_FLAGS -m32) That assumes that the default setup would build 64-bit executabl

[CMake] External_Project_Add() and custom build configurations ?

I have just started using some externally supplied cmake projects in my cmake project. To do this I added these lines to my top level CMakeLists.txt file: include(ExternalProject) ExternalProject_Add(external_proj PREFIX${CMAKE_BINARY_DIR}/external_proj SOURCE_DIR

[CMake] Strange behaviour with -D option

Hello everybody, there is a behaviour I do not understand when using cmake with -D option. In my project I defined a few CACHE variables. One of them is GUI to specify whether or not my project should be built with graphical library support. So in my main CMakeLists.txt I wrote something like

Re: [CMake] Post-build copy

Forget my question. I placed my add_custom_command at th wrong place ... sorry Eric pellegrini a écrit : Hello everybody, I build a static fortran library using CMake 2.8.0. Once the built is done I would like to copy the library archive and its related Fortran mod files stored in say, my_d

[CMake] integrating separate packages in one "superbuild" eclipse project

Hello, we use CMake to build several libraries and applications for an embedded Linux target with a cross compile toolchain. Recently we separated this from one huge source tree to one standalone project for each library and application, each in its own Git repository. The classical approach for

[CMake] Post-build copy

Hello everybody, I build a static fortran library using CMake 2.8.0. Once the built is done I would like to copy the library archive and its related Fortran mod files stored in say, my_dir1, in another directory say, my_dir2. Looking on the mailing list and on the web, I tried the following bu

[CMake] CPACK NSIS Destination Directory

Hi, I've been using CPack to generate NSIS installers. On my Windows 7 64-bit development platform this works perfectly. When I started building the release and generating the packages on our build server (also Windows 7 64-bit) things aren't quite as smooth. The installer is generated fine, bu

[CMake] ExternalProject, Install command

Sorry about possible double sending, I guess my first mail to this list didn't come through. I try to cross compile ppp as an external project. The install command is INSTALL_COMMAND make BINDIR=${EXTERNAL_PREFIX}/bin MANDIR=${EXTERNAL_PREFIX}/man INSTALL='/usr/bin/install --strip-program=$