That seems like it should work, but it actually does not.
There's two types of precedence in CMake.
1. Textual -- as CMake munches through a project and its subdirectory,
it generates a build system where the build order is the same as the
textual order. In a single process build, for example:
I meant to say 'the approach you use doesn't work, because imported
libraries are targets to are targets to which you CANNOT add
dependencies.
On Tue, Jun 26, 2012 at 9:33 AM, Kent Williams
nkwmailingli...@gmail.com wrote:
That seems like it should work, but it actually does not.
There's two
On Tuesday 26 June 2012, Kent Williams wrote:
I meant to say 'the approach you use doesn't work, because imported
libraries are targets to are targets to which you CANNOT add
dependencies.
This should work since I think cmake 2.8.4.
http://public.kitware.com/Bug/view.php?id=10395
Or am I
If I understand what's going on in that bug report, yes
add_dependency(imported_library EP_target) should work. But I found
that in fact it did not. So maybe that is a bug; if this was fixed in
2.8.4, I don't understand why I still have a problem.
On Tue, Jun 26, 2012 at 11:12 AM, Alexander
On Saturday 23 June 2012, Stefan Reuschl wrote:
Am 22.06.2012, 20:21 Uhr, schrieb Kent Williams
nkwmailingli...@gmail.com:
OK, I guess.
The only reason I bring this up is ITK. If you're familiar with the
ITK build process, it has a 'module' concept -- not a module in the
CMake sense
Am 22.06.2012, 20:21 Uhr, schrieb Kent Williams
nkwmailingli...@gmail.com:
OK, I guess.
The only reason I bring this up is ITK. If you're familiar with the
ITK build process, it has a 'module' concept -- not a module in the
CMake sense (where it is a library intended for runtime loading),
Say I have an ExternalProject that generates several libraries
ExternalProject_Add(foo
# the usual mumbo jumbo
)
set(foo_LIBRARIES)
# foo makes 3 libraries
foreach(lib a b c)
# import the libraries
add_library(${lib} STATIC IMPORTED)
# tell CMake where the library file is
On Fri, Jun 22, 2012 at 11:33 AM, Kent Williams
nkwmailingli...@gmail.comwrote:
Say I have an ExternalProject that generates several libraries
ExternalProject_Add(foo
# the usual mumbo jumbo
)
set(foo_LIBRARIES)
# foo makes 3 libraries
foreach(lib a b c)
# import the libraries
OK, I guess.
The only reason I bring this up is ITK. If you're familiar with the
ITK build process, it has a 'module' concept -- not a module in the
CMake sense (where it is a library intended for runtime loading), but
in the sense that the build process is modular. Each of the ITK
libraries is
