[vtk-developers] Remote Module Documentation

[David Gobbi]

Apologies, the last few messages in this thread had deviated away from
remote modules into entirely different territory...

On Wed, Feb 10, 2016 at 2:15 PM, Bill Lorensen <bill.lorensen at gmail.com>
wrote:

> The remote facility is very simple. Provide a foo.remote.cmake file
> and in your module create a module.cmake  to specify your vtk
> dependencies. The docs assume you want to make a conventional vtk
> module,. But, your module can do anything it wants.
>
> For example in ITK, there are the Sphinx and ITK Wiki Examples. These
> both have non-standard directory structures.
>
> I am currently working on a remote module for the vtk wiki examples.
> These will be buildable as a remote module or stand-alone. It is not
> that difficult.
>
> Stay tuned...
>
> Bill
>
>
> On Wed, Feb 10, 2016 at 4:00 PM, David Gobbi <david.gobbi at gmail.com>
> wrote:
> > 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
> >
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Search the list archives at:
> http://markmail.org/search/?q=vtk-developers
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/vtk-developers
> >
> >
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20160210/0abfd6f8/attachment.html>