[cmake-developers] ExternalProject can't have interface library as a dependency

[Andrey Pokrovskiy]

As far as I understand, IMPORT libraries are for different purposes.
They should be used for files that are already exist. In other words,
to import existing artifacts into the build system. I don't remember
the exact details, but last time I tried to use IMPORT library for
such purpose there was a cmake error saying that path (include dir or
library) not exists, while it should.
In my case openssl is also generated as a result of an external
project, so I have to use INTERFACE library.

On Tue, Apr 21, 2015 at 10:10 AM, Stephen Kelly <steveire at gmail.com> wrote:
> Andrey Pokrovskiy wrote:
>
>> [Moved from cmake users mailing list]
>>
>> I have the following construction:
>>
>> ExternalProject_Add(
>>         websockets_ep
>>         DEPENDS ev openssl
>>         ...)
>>
>> But it so happened, that "openssl" is an INTERFACE library. It is an
>> INTERFACE library, because I created it with add_library(openssl
>> INTEFACE) and then populated corresponding INCLUDE and LINK
>> properties.
>
> Sorry, I forgot to follow up on this on the user list.
>
> You probably want an IMPORT library instead of an INTERFACE one. That might
> already work for your dependency case with existing cmake releases.
>
> Thanks,
>
> Steve.
>
>
>
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake-developers