[vtk-developers] Remote Module Documentation

[David Gobbi]

Hi Steve,

I'm in a similar situation, I have repositories that I want to turn into
remote modules, but I also need to be able to build these modules outside
of VTK.  It's possible to do this (I know because I've done it) but it's
messy.  There doesn't seem to be a clean way to build proper VTK modules on
top of an existing binary VTK.

 - David


On Wed, Feb 10, 2016 at 12:50 PM, Steve Pieper <pieper at isomics.com> wrote:

> Hey Bill -
>
> Agreed, this is cool - it should work for a lot of cases.  Not sure it
> exactly works for my use case though, which at least at first is to use
> this code in a Slicer extension. This means that it's a library that's
> built after the general purpose VTK is already built.  Also because it's
> part of a Slicer extension there's a different directory layout (the actual
> C++ code is a couple directories below the top of the git repository).
> Plus there's other stuff in the CMakeLists.txt files (which might confuse
> the remote module build?).  Is there a way to use the same code and same
> repository in both scenarios?
>
> Thanks,
> Steve
>
> On Wed, Feb 10, 2016 at 2:36 PM, Will Schroeder <
> will.schroeder at kitware.com> wrote:
>
>> very very nice Bill, thanks
>>
>> On Wed, Feb 10, 2016 at 11:42 AM, Bill Lorensen <bill.lorensen at gmail.com>
>> wrote:
>>
>>> Steve,
>>>
>>> I updated the remote module documentation. Let me know of it helps.
>>>
>>> Bill
>>> http://www.vtk.org/Wiki/VTK/Remote_Modules
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20160210/17449337/attachment-0001.html>