[vtk-developers] New module system preview

[Bill Lorensen]

+1

On Fri, Nov 9, 2018, 10:59 AM Jean-Christophe Fillion-Robin <
jcfr at kitware.com wrote:

>
> --------------------
> > > * Building any VTK module either externally or along with the VTK
> project
> > > ?  (e.g this will be useful for creating python wheels)
>
> > I'm not sure the use case is clear to me. How are Python wheels related
> to remote modules?
>
> As of today, it is possible to distribute and package part of VTK
> independently. this is already done for the VTKOpenVR module. See [1]
>
> [1]
> https://github.com/Kitware/VTK/blob/4cb368df22c2db23ed230f743422fcfd78570229/Rendering/OpenVR/CMakeLists.txt#L1-L9
>
> The comment of David "VTK can be built kit-by-kit instead of all at once,
> is a logical extension of the multiple package idea" also capture this
> idea.
>
> From a user perspective, I see remote module as in "VTK module source
> stored outside of VTK source tree" exactly the same way as regular module.
> Ideally, a "project" command as well as a "find_package(VTK ... )" with
> the expected dependency would be written in every VTK module. The only
> exception would be a "VTKCore" module providing the build system
> infrastructure.
>
>
> --------------------
>
> > I love the ***idea*** of remote modules but sort of hate them in
> practice. I'm not sure if there is a way to make them work. Maybe someone
> knows a way.
> > Right now a change in VTK is as simple as one commit to one repo.
>
> This shouldn't change. The key idea here is that the underlying
> build-system should treat them the same way. The only different is that the
> source happen to already be available.
>
>
>
>
> On Fri, Nov 9, 2018 at 12:05 PM Prabhu Ramachandran <
> prabhu at aero.iitb.ac.in> wrote:
>
>> On 11/8/18 3:15 PM, David Gobbi wrote:
>>
>> On Thu, Nov 8, 2018 at 12:18 PM Ben Boeckel <ben.boeckel at kitware.com>
>> wrote:
>>
>>>
>>> > * Building any VTK module either externally or along with the VTK
>>> project
>>> > ?  (e.g this will be useful for creating python wheels)
>>>
>>> I'm not sure the use case is clear to me. How are Python wheels related
>>> to remote modules?
>>>
>>
>> Package managers like to be able to subdivide VTK into multiple packages.
>> Being able to modularize the build itself, so that VTK can be built
>> kit-by-kit
>> instead of all at once, is a logical extension of the multiple package
>> idea.
>> If I recall correctly, the CI system for pypi was failing to build VTK
>> due to
>> timeouts (I'm not sure what the workaround was, I suspect that Prabhu
>> built the wheels manually).
>>
>> Yes, I built the wheels with the VTKPythonPackage, (
>> https://github.com/KitwareMedical/VTKPythonPackage), it is largely
>> automated but I did build it by hand and uploaded it.
>>
>> I am not sure if this is still broken with 8.2 and hope to check this
>> weekend.
>>
>> cheers,
>>
>> Prabhu
>>
> _______________________________________________
> 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:
> https://public.kitware.com/mailman/listinfo/vtk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/vtk-developers/attachments/20181109/7a7e9f3e/attachment.html>