[vtk-developers] And one include to rule them all

[Marcus D. Hanwell]

On Tue, Sep 4, 2012 at 2:17 PM, Brad King <brad.king at kitware.com> wrote:
> On 09/04/2012 02:13 PM, Marcus D. Hanwell wrote:
>> For this we can introduce the equivalent of what VTK does when
>> building against a build tree - adding all depended upon module paths
>> to the include path of the compiler.
>
> So we're making the include path for the applications longer in
> order to make VTK's internal build include paths shorter?  That
> seems backwards to me.

That isn't what I said. Applications can use the full paths in their
code where they wish to, but we can retain a path where no application
code needs to change. Reducing the difference between the two ways of
building against VTK, allowing us to reduce complexity there, reducing
compilation time by not adding so many include paths during VTK
builds. It would be nice to be able to more easily see what module a
class is from without having to go find it in the tree.

Marcus