Hi Tom,<div><br></div><div>I set up a Mac dashboard. I'll get some other platforms build soon. It does have some compile issues that need to be addressed.</div><div><br></div><div><a href="http://www.cdash.org/CDash/buildSummary.php?buildid=832602">http://www.cdash.org/CDash/buildSummary.php?buildid=832602</a><br>
<br><div class="gmail_quote">On Mon, Jan 24, 2011 at 3:47 PM, tom fogal <span dir="ltr"><<a href="mailto:tfogal@sci.utah.edu">tfogal@sci.utah.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">David Partyka <<a href="mailto:david.partyka@kitware.com">david.partyka@kitware.com</a>> writes:<br>
> Hi Tom,<br>
><br>
> This looks like a very cool contribution! To get this moving forward<br>
> I am in the process of setting up some dashboards that will build<br>
> your VTK fork so we can see how the tests do on a few platforms. One<br>
> of us will also contact you about code review and how to best get<br>
> this integrated.<br>
<br>
</div>I had been caught up in deadlines but should slowly gain some time to<br>
finish up + correct this code over the next couple weeks. I still<br>
consider it incomplete... but I'm curious about the status. Has this<br>
dashboard been set up? What problems has it uncovered / how can I view<br>
them?<br>
<br>
Thanks,<br>
<br>
-tom<br>
<br>
(P.S. The interactive http access has been taken down, FWIW, but you'd<br>
want to use the git transport anyway.)<br>
<div><div></div><div class="h5"><br>
> On Mon, Jan 10, 2011 at 3:57 PM, tom fogal <<a href="mailto:tfogal@sci.utah.edu">tfogal@sci.utah.edu</a>> wrote:<br>
><br>
> > Ping!<br>
> ><br>
> > I imagine this initially went out while many were on vacation. Hoping<br>
> > people are back now...<br>
> ><br>
> > -tom<br>
> ><br>
> > tom fogal <<a href="mailto:tfogal@sci.utah.edu">tfogal@sci.utah.edu</a>> writes:<br>
> > > Hi,<br>
> > ><br>
> > > I'm forwarding this along again, without the patches attached, because<br>
> > > they made the message so large that it got stuck in a moderation queue.<br>
> > ><br>
> > > -tom<br>
> > ><br>
> > > ------- Forwarded Message<br>
> > ><br>
> > > Reply-To: <a href="mailto:tfogal@sci.utah.edu">tfogal@sci.utah.edu</a><br>
> > > From: tom fogal <<a href="mailto:tfogal@sci.utah.edu">tfogal@sci.utah.edu</a>><br>
> > > To: <a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a><br>
> > > cc: <a href="mailto:pugmire@ornl.gov">pugmire@ornl.gov</a><br>
> > > Subject: Use (`new') GLEW in VTK?<br>
> > > MIME-Version: 1.0<br>
> > > Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"<br>
> > > Content-ID: <<a href="mailto:3675.1293055749.0@shigeru.sci.utah.edu">3675.1293055749.0@shigeru.sci.utah.edu</a>><br>
> > > Date: Wed, 22 Dec 2010 15:10:12 -0700<br>
> > ><br>
> > > - ------- =_aaaaaaaaaa0<br>
> > > Content-Type: text/plain; charset="us-ascii"<br>
> > > Content-ID: <<a href="mailto:3675.1293055749.1@shigeru.sci.utah.edu">3675.1293055749.1@shigeru.sci.utah.edu</a>><br>
> > ><br>
> > > I've been working on a VTK hack in recent days, and given the "Render<br>
> > > tests ... Mesa features" thread, I figured now was a good time to bring<br>
> > > it to light.<br>
> > ><br>
> > > I'm working with the VisIt team and trying to help figure out our best<br>
> > > route forward with a long-overdue VTK upgrade. One of the issues we<br>
> > > hit is with offscreen rendering. It seems the `system' GL + Mangled<br>
> > > Mesa setup has been allowed to atrophy in recent versions of VTK. This<br>
> > > puts us in a bit of a bind, as the feature is critical for us.<br>
> > ><br>
> > > For various reasons, we must delay the choice of GL library until<br>
> > > runtime. Thus any sort of compile-time solution (i.e. building one<br>
> > > "Mesa+VTK-based binary" and one "GL+VTK-based binary") isn't going to<br>
> > > work for us. We also hit the issue that GLEW 1.x -- which we use for<br>
> > > some of our code that performs custom rendering -- was making the above<br>
> > > choice at compile-time.<br>
> > ><br>
> > > We've been working with GLEW upstream to get a version of GLEW that<br>
> > > does not utilize an OpenGL library at compile-time at all. Instead, it<br>
> > > dlopen()s (or similar) the GL library and loads function pointers that<br>
> > > way. This would obviate the need to even link an OpenGL library at<br>
> > > all. This modified version will turn into GLEW version 2 in the first<br>
> > > quarter 2011.<br>
> > ><br>
> > > We'd like to get VTK doing the same thing we do. I attached a (hacky)<br>
> > > patch series that should give you the gist of what we're thinking<br>
> > > about. There's some things still missing (notably, the CMake machinery<br>
> > > to avoid linking -lGL or -lMesaGL at all), but I tested a couple of<br>
> > > the VTK example programs and they seem to be okay. We could speak at<br>
> > > length about what's still needed and why this is a Good Thing, if you'd<br>
> > > like (given the aforementioned thread -- one nice bonus: just set an<br>
> > > env var or command line option, and you can test with a new GL: no<br>
> > > recompilation required!).<br>
> > ><br>
> > > I'd like to appeal to the VTK developers that we adopt a<br>
> > > corrected-version of the attached patchset into VTK. We (the VisIt<br>
> > > team) have had a lot of custom hacks to VTK over the years, and,<br>
> > > frankly, most if not all of us hate it. We'd really like to start<br>
> > > aligning a bit better, and now seems like a great time, since we are<br>
> > > contemplating a VTK upgrade.<br>
> > ><br>
> > > The patch series is also available online, if you prefer that:<br>
> > ><br>
> > > <a href="http://shigeru.sci.utah.edu:1234/?p=vtk.git;a=summary" target="_blank">http://shigeru.sci.utah.edu:1234/?p=vtk.git;a=summary</a><br>
> > > git://<a href="http://shigeru.sci.utah.edu/vtk.git" target="_blank">shigeru.sci.utah.edu/vtk.git</a><br>
> > ><br>
> > > Thanks for your consideration,<br>
</div></div></blockquote></div><br></div>