Re: [CMake] Shared library from ExternalProject

> However, that would still not make externals from > a .tar.gz being rebuilt if their archive was changed. Am I right? Yes, you're right, the UPDATE step is available only for git and svn. On Wed, Sep 16, 2015 at 3:22 PM, Tino Mettler wrote: > On Tue, 2015-09-15 at

Re: [CMake] Shared library from ExternalProject

On Tue, 2015-09-15 at 16:32 +0200, Tamás Kenéz wrote: > > it would be nice to know if the usage of add_library(foo SHARED > > IMPORTED) is the way to go in this case. > > I wouldn't think this is the way to go. One thing we love CMake for is that > it separates the concerns of the library and the

Re: [CMake] Shared library from ExternalProject

Hi, it would be nice to know if the usage of add_library(foo SHARED IMPORTED) is the way to go in this case. find_package() seems to be useless, as it requires that the external library is already present when cmake is invoked, which is not the case with an external project. So it seems like I

Re: [CMake] Shared library from ExternalProject

> it would be nice to know if the usage of add_library(foo SHARED > IMPORTED) is the way to go in this case. I wouldn't think this is the way to go. One thing we love CMake for is that it separates the concerns of the library and the consumer target so it's best to stick to find_package. This is

[CMake] Shared library from ExternalProject

Hi, I'm thinking about a solution to use separate projects as source archives and include it into the main cmake build. I looks like ExternalProject_Add() can handle this. However, there seems to be no standard way to use shared C/C++ libraries in an external project. Is there a basic example