Hi,
I was solving a similar problem in our setup at work. The problem was
that the parent couldn't know in advance which libraries will be
imported by children. Conceptually speaking, I solved this by creating
my own set of global properties which contain all necessary details
about the libraries
On Friday 09 March 2012, Petr Kmoch wrote:
Hi,
I was solving a similar problem in our setup at work. The problem was
that the parent couldn't know in advance which libraries will be
imported by children. Conceptually speaking, I solved this by creating
my own set of global properties which
I just did the same thing as Petr,
Hopefully, we can do it gracefully with 2.8.8.
Thanks~~
On Fri, Mar 9, 2012 at 10:48 AM, Alexander Neundorf a.neundorf-w...@gmx.net
wrote:
On Friday 09 March 2012, Petr Kmoch wrote:
Hi,
I was solving a similar problem in our setup at work. The problem
Hi,
Imported library has scope in the directory in which it is created and
below.
If I want to use this library in parent scope, what should I do?
for example,
top CMakeLists.txt
add_subdirectory(sub)
add_executable(myapp main.cpp)
target_link_libraries(myapp imported_lib)
sub CMakeLists.txt
On 08.03.12 19:24:00, Cong Ma wrote:
Hi,
Imported library has scope in the directory in which it is created and
below.
If I want to use this library in parent scope, what should I do?
Add the imported library in the top-level cmake file, not a
subdirectory.
Andreas
--
Powered by
