[vtk-developers] New module system preview

[David Thompson]

>>> - 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?

	David