[vtk-developers] Remote Module Documentation

[David Gobbi]

I was about to reply, but Ben's response is better than what I'd drafted.
But that won't stop me from adding a couple more points:

The module macros are not as well encapsulated as they could be (they
require some undocumented cmake variables to be set).  Also, in addition to
the fact that all the macros themselves might not be exported yet, I don't
know if all the necessary info for built modules is exported, either
(especially for "install").

I hadn't even thought about CMake 3, but the extra properties will
definitely be a huge help.

 - David


On Wed, Feb 10, 2016 at 1:50 PM, Ben Boeckel <ben.boeckel at kitware.com>
wrote:

> On Wed, Feb 10, 2016 at 15:35:41 -0500, Berk Geveci wrote:
> > This would be a great thing to have. Is the issue on the CMake
> > infrastructure side?
>
> Yeah. It's essentially the same problem ParaView has with an external
> VTK: VTK doesn't export all of its infrastructure macros properly
> (particularly testing and external data) in an install tree. There are
> probably other assumptions laying around that other projects trip up on
> (e.g., some setting VTK has which another project might want to change
> or the fact that VTK is built from within VTK's source tree). I don't
> know that an exhaustive (or comprehensive) list of issues exists. It
> will be something that will kept in mind when CMake 3 features are used
> in the module system.
>
> --Ben
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20160210/a351c959/attachment.html>