[CMake] Most better way to rebuild library if property changed

Hi, let say I have C library and I wish set difference "-D" options to this library ( must recompile library ) and exe should not known about those options. Scheme: lib + -DFEATURE1 && -DFEATURE2 -> lib with FEATURES 1 & 2 -> exe0 lib + -DFEATURE2 && -DFEATURE3 -> lib with FEATURES 2 & 3 -> ex

Re: [CMake] Determine dependency between targets

Hi Jörg, I am not sure if there is a way to do this via cmake, maybe there is and I don't know it, but I think you need to keep an eye on such things "manually" in a way. You could use ldd or readelf to see the exact dependencies of a library in linux. All the best, Angeliki On Wed, Jul 16, 20

[CMake] Configure separate from generate on the command line

Hi. We have a huge project which are using cmake. To resolve cross dependencies the cmake we are running it in two phases: 1. Configure (only), interrupted by “SEND_ERROR": In that phase CMakeCache.txt are created and it is used by next phase. 2. Standard cmake run (cache variables are set,

Re: [CMake] RPM packaging dependencies expressed in subdirectories

On 16.07.2014 16:37, Thibault Hild wrote: Thanks Nils for the hint. I guess you had to use Cmake constructs like: if("new dep" MATCHES "a regex built with ${pack_deps}") in order to decide whether a new dependency is allowed. As I am quite new to CMake functions, can you detail a bit how do you

[CMake] Determine dependency between targets

Hi! i am looking for a way to determine REAL LINKER dependencies between an application and static libraries for use with gcc. the include dependencies and cmake dependencies are quite good to determine. For the linker is more or less the question, against which libraries i should link. This i

Re: [CMake] Fails for Solaris

Amos, I just tried on a Sun Blade 1500 running Solaris 10 8/11 with an UltraSPARC IIIi using SolarisStudio 12.2 and 12.3. Both were able to configure and build successfully using both the bootstrap, /path/to/source/bootstrap && gmake, and and cmake, cmake /path/to/source && gmake, so it can be do

Re: [CMake] RPM packaging dependencies expressed in subdirectories

Thanks Nils for the hint. I guess you had to use Cmake constructs like: if("new dep" MATCHES "a regex built with ${pack_deps}") in order to decide whether a new dependency is allowed. As I am quite new to CMake functions, can you detail a bit how do you operate such validation ? Is there some sor

Re: [CMake] RPM packaging dependencies expressed in subdirectories

On 16.07.2014 15:08, Thibault Hild wrote: Hello, I'm quite new to CMake and after experimenting a bit, I am currently considering a way to express RPM dependencies in subdirectories instead of specifying them at the top level. After googling a bit, I did not find something that fulfills my ex

[CMake] RPM packaging dependencies expressed in subdirectories

Hello, I'm quite new to CMake and after experimenting a bit, I am currently considering a way to express RPM dependencies in subdirectories instead of specifying them at the top level. After googling a bit, I did not find something that fulfills my expectations but I have probably missed a post or

Re: [CMake] opencl and visual studio

I’m rather new to CMake myself, so I’d pretty much do what you could as well: look through the docs. All I know is that much much more complicated things can be done with CMake, and many things can be done multiple ways. I’d rather call on the other mail list users to answer this one: how to co

[CMake] Install path for package files

So when I make a library that I want to be findable with cmake, I'd like the cpack system to work such that the module file is installed into the cmake module search path unless specified otherwise. I gather I need to create a BlahModule.cmake file that implements the package finding stuff. I wan