[vtk-developers] Slight behavioral change in WhatModulesVTK.py (new module system)?

[Andrew Maclean]

I am surprised and amazed this works with the new system.
When I wrote it, it:
1) Only looked at the header files in your code and, from their name,
worked out the module to use. Ad a consequence of this we had to manually
include e.g. some modules like the OpenGL stuff.
2) Does detect modules excluded from the wrapping.
3) It was written before external modules were introduced so it may not
properly work with them.

The intent was to provide to the user a guide as to what modules should be
included so they may still have to add extras.

Andrew



>
> ---------- Forwarded message ----------
> From: Ben Boeckel <ben.boeckel at kitware.com>
> To: Elvis Stansvik <elvis.stansvik at orexplore.com>
> Cc: vtkdev <vtk-developers at vtk.org>
> Bcc:
> Date: Fri, 11 Jan 2019 13:30:42 -0500
> Subject: Re: [vtk-developers] Slight behavioral change in
> WhatModulesVTK.py (new module system)?
> On Fri, Jan 11, 2019 at 19:13:29 +0100, Elvis Stansvik wrote:
> > Ah yes, but what about modules that are excluded from wrapping?
>
> Indeed. They do have that property skipped. This is at line
> vtkModule.cmake:2997 (give or take). I actually am not sure how third
> party libraries would appear here as well since they almost always have
> a separate header installation step for the header VTK exposes for them
> (e.g., `vtk_hdf5.h`).
>
> --Ben
>
>
>
> --
___________________________________________
Andrew J. P. Maclean

___________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://vtk.org/pipermail/vtk-developers/attachments/20190112/ba3ee9b5/attachment-0001.html>