[vtk-developers] eeloo

[Ken Martin]

I guess it depends on which is more likely to get done. Moving some
buildbot scripts into VTK sounds fairly easy. Creating CMake code to
discover compiler flags and use them or not might take longer. Right now
compiler warnings during normal development seems iffy as many third party
headers emit warnings that without ctest's filtering we can get a lot of
false positives. More so for ParaView than VTK but both of them suffer from
it.

On Tue, Sep 11, 2018 at 4:20 PM, Ben Boeckel <ben.boeckel at kitware.com>
wrote:

> On Mon, Sep 10, 2018 at 14:52:11 -0400, Utkarsh Ayachit wrote:
> > > And this highlights Utkarsh's good idea to have the toolkit specific
> > > buildbot scripts or some of them in the toolkit tree. That way we
> > > could turn on the flag for that topic to test it out without
> > > impacting the other topics in testing or master.
> >
> > Indeed! Once Ben has recovered from the backlog, would be great to
> > prioritize it :).
>
> Would it not be better to have VTK discover and add warning flags during
> configure rather than specifying any warning flags via `CMAKE_CXX_FLAGS`
> in buildbot? This means the warnings also show up during normal
> development.
>
> --Ben
>



-- 
Ken Martin PhD
Distinguished Engineer
Kitware Inc.
101 East Weaver Street
Carrboro, North Carolina
27510 USA

This communication, including all attachments, contains confidential and
legally privileged information, and it is intended only for the use of the
addressee.  Access to this email by anyone else is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any
action taken in reliance on it is prohibited and may be unlawful. If you
received this communication in error please notify us immediately and
destroy the original message.  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/vtk-developers/attachments/20180912/09b8e3cb/attachment.html>