I played around a bit more with this and I'm getting more confused. Using cmake-gui v2.8.7, I configured paraview (a version from last week) and saw the VTK_USE_X option there. Without changing anything, I did another configure and the VTK_USE_X option disappears.<br>
<br>Andy<br><br><div class="gmail_quote">On Thu, Jun 7, 2012 at 4:01 PM, Andy Bauer <span dir="ltr"><<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you turn off PARAVIEW_BUILD_QT_QUI then VTK_USE_X disappears as an option. Checking CMakeCache.txt it is still set to ON. If I turn back PARAVIEW_BUILD_QT_GUI though the VTK_USE_X disappears.<br><br>From past builds without the GUI and with mesa I would choose to not build the gui, use mesa, and set to not use x. With the current build it looks like I can't do this anymore in this order. <br>
<span class="HOEnZb"><font color="#888888">
<br>Andy</font></span><div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Thu, Jun 7, 2012 at 3:50 PM, Marcus D. Hanwell <span dir="ltr"><<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Wed, Jun 6, 2012 at 2:47 PM, Fabian, Nathan <<a href="mailto:ndfabia@sandia.gov" target="_blank">ndfabia@sandia.gov</a>> wrote:<br>
> In a git pull from yesterday, it appears that VTK_USE_X is being marked<br>
> internal somehow, so that I can't set it from ccmake. I am trying to<br>
> setup OSMESA and normally I think when checking OPENGL_HAS_OSMESA, it<br>
> changes VTK_USE_X from internal to visible, but I'm not really sure where<br>
> to look for that.<br>
><br>
> Any help?<br>
><br>
</div>Why do you think VTK_USE_X is set to internal? I refactored the OS<br>
Mesa support in VTK (and hence ParaView). I just pulled ParaView<br>
master, made a clean build directory with no arguments (cmake<br>
~/src/ParaView), and VTK_USE_X is there (in advanced) and turned ON.<br>
<br>
You can see a selection of dashboard submissions including<br>
<a href="http://open.cdash.org/buildSummary.php?buildid=2339963" target="_blank">http://open.cdash.org/buildSummary.php?buildid=2339963</a> on VTK that<br>
test OS Mesa each night, and they are passing. I preserved the same<br>
variables (searching MESA in the cache shows VTK_OPENGL_HAS_OSMESA<br>
etc), so that the wiki instructions continued to work.<br>
<br>
I can look into this further, but I am not aware of any CMake code<br>
making these variables internal (and in my local tests they are<br>
advanced as they have always been). I would appreciate feedback if any<br>
regressions were introduced I can get them fixed up.<br>
<br>
Thanks,<br>
<br>
Marcus<br>
<div><div>_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org" target="_blank">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>