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

Bill Lorensen bill.lorensen at gmail.com
Tue Sep 4 14:27:18 EDT 2012


+1 for Brad's comments. What is the problem we are trying to solve?

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.
>
> What has not been summarized in this thread is the justification
> for doing this at all.
>
> -Brad
> _______________________________________________
> 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
>
>


-- 
Unpaid intern in BillsBasement at noware dot com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20120904/bf6f64f0/attachment.html>


More information about the vtk-developers mailing list