[CMake] Calling find_package(self) for in-project builds

[Walter Gray]

Very true, but adding the option of sometimes having the targets be aliases
and sometimes having them be imported means that protobuf-module.cmake.in
has to get much more complicated and means that we have to conditionally
include protobuf-targets.cmake
I'd like to minimize the differences between building the examples
independently and building them as part of a combined build.

On Thu, Jun 2, 2016 at 10:40 PM Konstantin Podsvirov <
konstantin at podsvirov.pro> wrote:

> Hello.
>
> 8:34, 3 june 2016 г., Walter Gray <chrysalisx at gmail.com>:
>
> Interesting idea, that could be possible.
>
>
> Possible, but realy need? It can be alternative. Now we can use ALIASES
> for build tree configuration - It's work (I check)
>
> On Thu, Jun 2, 2016 at 8:45 PM Dan Liew <dan at su-root.co.uk> wrote:
>
> > What would be the suggested way to handle this?
>
> Couldn't you build the examples using CMake's ``ExternalProject``
> module [1] and have that build after the main project has finished
> building?
>
> [1] https://cmake.org/cmake/help/v3.5/module/ExternalProject.html
>
>
>
>
> --
>
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20160603/8cb262f1/attachment.html>