[vtk-developers] Wrapping/Tools

[David Cole]

On Thu, Jun 21, 2012 at 3:29 PM, David Gobbi <david.gobbi at gmail.com> wrote:

> Going with the general flow of modularization, I'm wondering if the
> wrapping tools like Wrapping/vtkWrapPython.c should be moved to a new
> directory called Wrapping/Tools.
>
> Pros: A Wrapping/Tools directory would nicely fit the two-level
> directory structure that VTK has adopted.
>
> Cons: Wrapping/Tools can't be made into a proper "module" as far as I
> understand it, because it isn't a library for other modules to link
> to.  Rather, it is a set of executables that other modules need to
> execute during the build process.
>
> Main reason that I'm wondering is that I have some changes to the
> wrapper tools that I want to merge, and they include an overhaul of
> Wrapping/CMakeLists.txt.  So it seems to make sense that if the
> wrapper tools are going to be moved, then the move should be done
> prior to the merge.
>
>  - David
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>
This sounds reasonable to me. The "con" you list doesn't seem like that
much of a con to me. Even if you have to make a dummy module library with a
dummy function in it, I'd still say the pro outweighs it.

Cheers,
David C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20120621/a371b1ce/attachment.html>