-boun...@cmake.org On Behalf Of Michael Jackson
Sent: Thursday, 19 March 2009 19:55
To: Cmake Mailing List
Subject: Re: [CMake] How to describe lib dependencies when a lib has different
possible implementations?
Not sure you want to go down this path but the CMake files in the SVN
repository of Boost has
e@cmake.org
Objet : Re: [CMake] How to describe lib dependencies when a lib has
different possible implementations?
If you want to compile two execs, one for each static library you can
use a two element list and go "for_each" over each library and create
two execs. Otherwise you can
intaining it by hand).
Alexandre
-Message d'origine-
De : cmake-boun...@cmake.org De la part de Christopher Harvey
Envoyé : jeudi 19 mars 2009 19:04
À : Alexandre Feblot
Cc : cmake@cmake.org
Objet : Re: [CMake] How to describe lib dependencies when a lib has
different possible implementations?
eudi 19 mars 2009 19:04
À : Alexandre Feblot
Cc : cmake@cmake.org
Objet : Re: [CMake] How to describe lib dependencies when a lib has different
possible implementations?
If you want to compile two execs, one for each static library you can
use a two element list and go "for_each" over
If you want to compile two execs, one for each static library you can
use a two element list and go "for_each" over each library and create
two execs. Otherwise you can just hardcode it into cmake.
Alexandre Feblot wrote:
Hi,
in fact, in my current system, the implementation to use is prett
Hi,
in fact, in my current system, the implementation to use is pretty hardcoded in
each executable makefile, in the link line. There is no automatic lib
dependency management.
Alexandre
-Message d'origine-
De : cmake-boun...@cmake.org De la part de Christopher Harvey
Envoyé : jeud
Hi,
Interesting question. You said that
"only one of them has to be used in every executable, the implementation
to use is determined by the executable."
These are static libraries, so how can the exec pick one if it isn't
even built? (As opposed to loading one dynamically)
Basically I'm still w
Hi,
I'm facing an issue while trying to port my current build system to
cmake and don't know is there is a way to solve it:
In our project, we build a bunch of static libs (about 360) and several
executables on them.
* one library, in the middle of the lib dependency chain, has in fact 2
diff
