[CMake] Discovering ExternalProject library dependencies?

Hello, Is there a convenient way to have CMake detect at build time additional libraries that need to be linked for an external project to work? For example, suppose I have ExternalProject_Add(Foo ...args...) which builds libfoo.a (which is an autotools package). Depending on the system on which

Re: [CMake] clear compile flags for a file

On Wed, Apr 10, 2013 at 1:37 PM, Ian Monroe wrote: > So I have the same problem as the person in this old thread: > http://www.cmake.org/pipermail/cmake/2009-August/031671.html > > I want to add some compile flags (currently using add_definitions) but > they mess up the rc.exe resource compiler.

[CMake] clear compile flags for a file

So I have the same problem as the person in this old thread: http://www.cmake.org/pipermail/cmake/2009-August/031671.html I want to add some compile flags (currently using add_definitions) but they mess up the rc.exe resource compiler. Doing something like: set_source_files_properties(hipchat.rc

Re: [CMake] nested replacement with @@

Another workaround is to make an intermediate variable in the CMakeLists.txt file and use this intermediate variable from the .in file. That elminates the nested @@'s. Clint On Wednesday, April 10, 2013 07:51:03 PM Eric Clark wrote: > Nico, > > I had this same problem at one point in time, b

Re: [CMake] nested replacement with @@

Nico, I had this same problem at one point in time, but was able to change it to the ${...} syntax which works beautifully. I know that you cannot use this syntax, but I will tell you that I did find a work-around for the nested @...@ syntax. The workaround is to run configure_file on the file

Re: [CMake] nested replacement with @@

2013/4/10 Eric Noulard > > 2013/4/10 Nico Schlömer > > >> Replacing the above line by >> >> @@PROJECT_NAME@_VERSION@ >> >> doesn't work however: The output file contains >> >> @Myproject_VERSION@ >> >> i.e., only the inner variable was replaced. >> >> How to fix this? >> > > May be it's a featur

Re: [CMake] nested replacement with @@

2013/4/10 Nico Schlömer > Hi all, > > in a ProjectContfigTemplate.cmake.in file, I'd like to have variables > such as ${${PROJECT_NAME}_VERSION}. In ${}-syntax, the nesting is > recognized properly, and this string would be replaced by, e.g., > "2.1". > > I know need to have ${}-variables in the

[CMake] nested replacement with @@

Hi all, in a ProjectContfigTemplate.cmake.in file, I'd like to have variables such as ${${PROJECT_NAME}_VERSION}. In ${}-syntax, the nesting is recognized properly, and this string would be replaced by, e.g., "2.1". I know need to have ${}-variables in the output file, so I tried to switch to the

Re: [CMake] COMPONENTS for export files

On Wednesday 10 April 2013, Nico Schlömer wrote: > Sounds pretty good! > > One question remains: > Suppose I have components A, B, C, where both A and B depend on C. > The link line that I'd pull in with > > FIND_PACKAGE(Mypackage COMPONENTS A B) > > Would be > , , , > where all of those could

Re: [CMake] CTest / CDash integration

ctest has long been quite "under-documented" There are some open issues in the bug tracker: http://public.kitware.com/Bug/view.php?id=10392 http://public.kitware.com/Bug/view.php?id=13836 What's needed is someone to go in and do the work to document it well. Until that happens, your bes

Re: [CMake] CTest / CDash integration

Probably someone else can give you a better answer, but I ended up doing the following: ctest \ --build-and-test "$SOURCE_DIR" "$BUILD_DIR" \ --build-generator "Unix Makefiles" --build-makeprogram make \ -j "$PARALLEL_JOBS" \ --build-options -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_C_COMPILER=

[CMake] Ralph Barth/AEH/DBS/GDB ist außer Haus.

Ralph Barth will be out of the office starting 10.04.2013 and will be returning on 11.04.2013. Ich werde Ihre Nachrichten nach meiner Rückkehr beantworten. WLLM related questions pls. contact Sebastian Neusüß and Jens Keil. Theo Price Feed from EDRE pls contact Jens Keil

Re: [CMake] CTest / CDash integration

Sorry, but I have to keep complaining about the documentation. Please excuse the ranting. Just one example from the manual: ctest --build-options: Add extra options to the build step. This option must be the last option with the exception of --test-command End of available information.

[CMake] Disable creation of uninstall link in windows start menu (CMAKE + CPACK + NSIS)

Hi, I like to disable the creation of the uninstall link in the windows start menu when using the NSIS generator in combination with CMAKE and CPACK. When executing the generated NSIS installer using the standard configuration of CPACK the uninstall link is automatically added to the window

Re: [CMake] INSTALL_INTERFACE question

Yeah, that's it. Thanks. That page was referenced by a recent kitware blog. http://www.kitware.com/blog/home/post/462 Clint - Reply message - From: "Stephen Kelly" Date: Wed, Apr 10, 2013 1:08 am Subject: [CMake] INSTALL_INTERFACE question To: Stephen Kelly wrote: > Where did you

Re: [CMake] INSTALL_INTERFACE question

Stephen Kelly wrote: > Where did you see the > example above? In an old commit message? It doesn't seem to be in the > code: Ah, I found and fixed it on the wiki page: http://community.kde.org/Frameworks/Epics/CMake_target_usage_requirements Thanks, Steve. -- Powered by www.kitware.com V

Re: [CMake] INSTALL_INTERFACE question

clin...@elemtech.com wrote: > > I'm playing with some of the new cmake 2.8.11 features and an example I > saw had this: > > set_property(TARGET foo PROPERTY >INTERFACE_INCLUDE_DIRECTORIES >"$" >"$" > ) > > I can see it put the expanded version of "${CMAKE_INSTALL_PR