Re: [CMake] CPack Multicore Usage

> > cause cpack does not "rebuild" the software again, it uses the compiled > software and just starts the "install" into its _CPack_Packages > subdirectories > Just running `cpack` does not. However, CMake does generate a "package" make target that is tied into your dependencies, so if instead o

Re: [CMake] How do I specify VTK minimum version?

You don't have to ask for a specific version. You can just do: find_package(VTK REQUIRED) if you don't really care what version is found. Or if you need >= 7, you can do it like that and then check what version was actually found, and error out yourself if it is too old. HTH, David C. O

Re: [CMake] How do I specify VTK minimum version?

Thank you for the answers. I used this script to fix my problem: find_package(VTK 7.1.0 QUIET) if (NOT VTK_FOUND) find_package(VTK 8.0.0 REQUIRED) endif() include(${VTK_USE_FILE}) Of course this will only work until there is a VTK 9.x.x version. -- Powered by www.kitware.com Please keep me

Re: [CMake] "Modern" approach to optional/multiple configurations?

Hi Again, I was asked to link to the background discussion for this (good point!). The actual post was: https://lists.boost.org/Archives/boost/2017/07/237490.php and there's quite a bit of talk in that thread and a few similarly-named others about CMake. This announcement seems to have stirre

Re: [CMake] CPack: Create debian packge for each sub-project

Here's a little trick I learned. Executing the custom target, "make package_target target=xyz", will build the target and call cpack to create the package. Additional parameters can be passed by putting the target value in quotes (make package_target target="xyz -j4"). Executing cpack causes the t

Re: [CMake] Append to property COMPILE_DEFINITIONS

On Mon, Jul 24, 2017 at 12:32 PM, Florian Lindner wrote: > > > Am 22.07.2017 um 15:36 schrieb Craig Scott: > > > > On Tue, Jul 18, 2017 at 8:50 PM, Florian Lindner > wrote: > > > > #Works, but I would prefer to have it just once for all targets and > at the top of

Re: [CMake] Boost is planning to switch from bjam to CMake!

Let's hope this try actually works. It was tried 8 years ago but some of the boost developers really fought the transition. Hopefully with the support of the steering committee it will work. Let's all welcome the boost devs into the CMake community with wide open arms. -- Mike Jackson [mike.ja

Re: [CMake] How do I specify VTK minimum version?

2017-07-24 12:23 GMT+02:00 Rolf Eike Beer : > Am Dienstag, 11. Juli 2017, 15:18:11 schrieb Victor Lamoine: >> Hi, >> >> I am using CMake to set up a VTK project. Our project requires VTK to be >> version 7.1 or newer. I'm using Ubuntu 16.04 with CMake 3.5.1. >> > >> find_package(VTK 7.1 REQUIRED) >

Re: [CMake] How do I specify VTK minimum version?

Am Dienstag, 11. Juli 2017, 15:18:11 schrieb Victor Lamoine: > Hi, > > I am using CMake to set up a VTK project. Our project requires VTK to be > version 7.1 or newer. I'm using Ubuntu 16.04 with CMake 3.5.1. > > find_package(VTK 7.1 REQUIRED) […] > The following configuration files were consi

[CMake] "Modern" approach to optional/multiple configurations?

Seen in the boost discussions on the CMake announcements: > > The rest can be implemented straightforwardly as cache options so that > > you can run cmake with options like > > > > -Dvalgrind=OFF -Dtransactional-memory=ON -Dsegmented-stacks=ON [-D…] > ... Secondly, in cmake 3 we try not to con

Re: [CMake] How do I specify VTK minimum version?

Hello, I am still stuck with this problem, I don't understand what's wrong. Is my question unclear? Do I not provide enough information? Please ask for additional information if I forgot something. Bye -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] CPack Multicore Usage

I think i had a wrong understanding of the cpack process itself. so i did a cmake configure and called cpack to build the software and generate the packages (deb, tgz) but better would be to configure, build with make -jx and then call cpack, cause cpack does not "rebuild" the software again, it