Re: [CMake] Interfacing cmake with 3rdparties package manager, and exclude them from ninja clean

Hello,Tx for the idea !That would work to "boostrap" the build but I'm not very fond of it due to it's "static" nature : it would run only once during the initial cmake run.We extract versionning information from git tags : in our current (slow) build system, a git update can trigger a "rpm"

Re: [CMake] Interfacing cmake with 3rdparties package manager, and exclude them from ninja clean

Maybe executing your script in configure time (execute_process)? On Fri, Jan 20, 2017 at 4:36 PM, wrote: > Hello, > > I'm working on a project where some of our libs depend on custom build of > some external libraries. > Those external libraries are managed through a

[CMake] Interfacing cmake with 3rdparties package manager, and exclude them from ninja clean

Hello,I'm working on a project where some of our libs depend on custom build of some external libraries.Those external libraries are managed through a repository manager similar to rpm (redhat package manager) which allows us to retrieve pre-compiled versions with related header files. (similar to