[vtk-developers] New module system preview

[Marcus D. Hanwell]

On Mon, Oct 29, 2018 at 2:23 PM David Thompson <david.thompson at kitware.com>
wrote:

> >>> - Instead of `module.cmake`, there are `vtk.module` and `vtk.kit`
> >>>   files. These are basically CMake argument lists, but no variable
> >>>   expansion is allowed. If there are optional dependencies, they must
> >>>   be private dependencies. Optional public dependencies indicate that
> >>>   a new module should be made instead.
> >>
> >> Is there a reason these things need to be separate files
> >> (vtk.module/vtk.kit) at all?
> >
> > The `vtk.kit` declares a kit. Membership into a kit is via `vtk.module`.
> > Example `vtk.kit`:
>
> Yes, but why can't these declarations for modules and kits be inside
> CMakeLists.txt as function calls instead of separate files?
>

Guessing, but likely because we still use a two-pass approach - scan
module/kit files, build up dep list, then actually add the things that are
enabled in the second pass.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/vtk-developers/attachments/20181029/019b02ba/attachment.html>