[vtk-developers] (no subject)

[David E DeMarle]

I'll turn examples off then on the cygwin build and we'll see how that goes
tonight.

We've got one minGW build on the dashboards and we've put in the time to
keep it green up to now. We should keep doing so as it takes minimal effort
and catches unique bugs from time to time.



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Thu, Mar 21, 2013 at 11:29 AM, Marcus D. Hanwell <
marcus.hanwell at kitware.com> wrote:

> On Thu, Mar 21, 2013 at 11:17 AM, David E DeMarle
> <dave.demarle at kitware.com> wrote:
> > On Wed, Mar 20, 2013 at 4:07 PM, David Cole <dlrdave at aol.com> wrote:
> >>
> >> The VTK Cygwin dashboard has this in its driving script:
> >>
> >>     //No X on this machine and no time to test if it works so silence
> >> failing tests
> >>     VTK_Group_Rendering:BOOL=OFF
>
> You should be able to build with the VTK_Group_Rendering turned off,
> trying that locally things look OK (I wonder if there are other
> settings that might affect this). The StandAlone group should be
> everything that doesn't require unusual external dependencies,
> Rendering largely pulls in OpenGL/windowing systems, MPI pulls in MPI.
> >>
> >> And the build shows errors:
> >>
> >>     http://open.cdash.org/buildSummary.php?buildid=2850639
> >>
> >>
> >> Questions:
> >>
> >> Is that the right way nowadays to turn Rendering off?
> >
> Yes, it is.
> >
> > Not sure here but it appears that standalone is "all of what you
> typically
> > expect from VTK" and not "just VTK's data processing sans rendering".
> > Marcus can you confirm.
>
> I can confirm confirm that anything with an OpenGL dependency should
> be in the rendering group, anything that is pretty stand alone
> (doesn't require big external dependencies, might include third party
> libs we build) is in StandAlone.
> >
> > It might be just that examples is on on this machine and those don't
> > understand its module dependencies.
> >
> That could be the case - I didn't try with Examples turned on.
> >>
> >> Is this a general problem with doing a build that has
> VTK_Group_Rendering
> >> OFF, or is it just the Cygwin build that has problems? (i.e., should
> this be
> >> something to worry about beyond Cygwin?)
> >
> >
> > See also the no render karego-at build. For that I turned off both
> > standalone and rendering and then turned on just a core module. Once
> Marcus
> > tells us how to do it properly I'll configure both machines the same and
> > we'll know if it is cygwin specific issue.
> >
> You can turn off all groups, and then just enable the one or two
> modules of interest (they will enable all of their required
> dependencies). The groups are intended as a convenience for
> developers, and roughly mimic some of the old VTK_USE_* options.
> >
> >> Does anybody even care about VTK on Cygwin? If so, could those who care
> >> contribute a dashboard that does have Rendering on? If not, let’s just
> stop
> >> running the one that doesn’t work anyway...
> >
> >
> > +1 for not testing (and thus claiming to support) cygwin, that dashboard
> has
> > been broken for years. Turning off rendering was my attempt a few months
> ago
> > to get by without digging in my heels.
> >
> > Unless their is a user out there who cares, I don't think we should spend
> > time on cygwin.
> >
> I don't use it, and to be honest would rather put energy into MinGW if
> we were going for GCC on Windows (not saying we need to due to the
> widespread availability of Visual Studio Express versions).
>
> Marcus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20130321/2f71c61c/attachment.html>