Re: [CMake] Disabling INSTALL target for subdirectory

2017-02-16 Thread Milan Ziegler
Hi Florent, thank you so much. EXCLUDE_FROM_ALL does indeed have the effect of ignoring any install() invocations from within the subdirectory. I remember stumbling across this option, but from the docs I didn't get the impression that this would affect the installation as well. Maybe the

Re: [CMake] Disabling INSTALL target for subdirectory

2017-02-16 Thread Florent Castelli
Use add_subdirectory(... EXCLUDE_FROM_ALL) to prevent anything in there to be installed by default. I had the issue in one project and it did fix it for us. Also, 3rdparty libraries should be tagged like that anyway to be built only when they are used by the main targets. /Florent On Feb 16,

Re: [CMake] Disabling INSTALL target for subdirectory

2017-02-16 Thread Domen Vrankar
2017-02-16 7:59 GMT+01:00 Milan Ziegler : > Hi, > > we are using the CMake install mechanism "install(...)" to copy all > relevant files and target binaries of the product into the CMake install > prefix folder, for further packaging. So far so good. > > We are also using

Re: [CMake] Disabling INSTALL target for subdirectory

2017-02-15 Thread Craig Scott
You can use the COMPONENT option to install() for your own project and then select a component-based package if you are packaging with CPack. We currently do this with builds that incorporate other projects with add_subdirectory() similar to your case. If you are using install as a build target

Re: [CMake] Disabling INSTALL target for subdirectory

2017-02-15 Thread Konstantin Podsvirov
Hello all!10:00, 16 February 2017 г., Milan Ziegler :Hi,we are using the CMake install mechanism "install(...)" to copy allrelevant files and target binaries of the product into the CMake installprefix folder, for further packaging. So far so good.We are also using several

[CMake] Disabling INSTALL target for subdirectory

2017-02-15 Thread Milan Ziegler
Hi, we are using the CMake install mechanism "install(...)" to copy all relevant files and target binaries of the product into the CMake install prefix folder, for further packaging. So far so good. We are also using several thirdparty libraries, hosting them inside our own repository and