Hi Nathan,<br><br>I just wanted to let you know that Marcus has fixed this and it's now in ParaView master. <br><br>Andy<br><br><div class="gmail_quote">On Thu, Jun 7, 2012 at 5:00 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">Good call, I think if we remove several lines from<br>
ParaViewCommon.cmake that lead to include(vtkUseX) then it should be<br>
much better. We should also remove that file from VTK too. I pushed a<br>
branch called fix-use-x-internal to the ParaView stage that fixes this<br>
issue.<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Jun 7, 2012 at 4:35 PM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
> It's probably in VTK_DEPENDENT_OPTION -- the options that it depends on must<br>
> not be cached. VTK_DEPENDENT_OPTION expects (I think) all of the "depends"<br>
> variables to be cache variables...<br>
><br>
><br>
><br>
> On Thu, Jun 7, 2012 at 4:26 PM, Marcus D. Hanwell<br>
> <<a href="mailto:marcus.hanwell@kitware.com">marcus.hanwell@kitware.com</a>> wrote:<br>
>><br>
>> I see it getting marked internal by tweaking this parameter, I will<br>
>> dig into why that would cause VTK_USE_X to be changed. It is a bug,<br>
>> but it may take me a little time to track down where in CMake this is<br>
>> being changed.<br>
>><br>
>> On Thu, Jun 7, 2012 at 4:23 PM, Andy Bauer <<a href="mailto:andy.bauer@kitware.com">andy.bauer@kitware.com</a>> wrote:<br>
>> > I played around a bit more with this and I'm getting more confused.<br>
>> > Using<br>
>> > cmake-gui v2.8.7, I configured paraview (a version from last week) and<br>
>> > saw<br>
>> > the VTK_USE_X option there. Without changing anything, I did another<br>
>> > configure and the VTK_USE_X option disappears.<br>
>> ><br>
>> > Andy<br>
>> ><br>
>> ><br>
>> > On Thu, Jun 7, 2012 at 4:01 PM, Andy Bauer <<a href="mailto:andy.bauer@kitware.com">andy.bauer@kitware.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> If you turn off PARAVIEW_BUILD_QT_QUI then VTK_USE_X disappears as an<br>
>> >> option. Checking CMakeCache.txt it is still set to ON. If I turn back<br>
>> >> 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<br>
>> >> build<br>
>> >> the gui, use mesa, and set to not use x. With the current build it<br>
>> >> looks<br>
>> >> like I can't do this anymore in this order.<br>
>> >><br>
>> >> Andy<br>
>> >><br>
>> >><br>
>> >> On Thu, Jun 7, 2012 at 3:50 PM, Marcus D. Hanwell<br>
>> >> <<a href="mailto:marcus.hanwell@kitware.com">marcus.hanwell@kitware.com</a>> wrote:<br>
>> >>><br>
>> >>> On Wed, Jun 6, 2012 at 2:47 PM, Fabian, Nathan <<a href="mailto:ndfabia@sandia.gov">ndfabia@sandia.gov</a>><br>
>> >>> wrote:<br>
>> >>> > In a git pull from yesterday, it appears that VTK_USE_X is being<br>
>> >>> > marked<br>
>> >>> > internal somehow, so that I can't set it from ccmake. I am trying<br>
>> >>> > to<br>
>> >>> > setup OSMESA and normally I think when checking OPENGL_HAS_OSMESA,<br>
>> >>> > it<br>
>> >>> > changes VTK_USE_X from internal to visible, but I'm not really sure<br>
>> >>> > where<br>
>> >>> > to look for that.<br>
>> >>> ><br>
>> >>> > Any help?<br>
>> >>> ><br>
>> >>> 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>
>> >>> _______________________________________________<br>
>> >>> Paraview-developers mailing list<br>
>> >>> <a href="mailto:Paraview-developers@paraview.org">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>
>> >><br>
>> >><br>
>> ><br>
>> _______________________________________________<br>
>> Paraview-developers mailing list<br>
>> <a href="mailto:Paraview-developers@paraview.org">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>
><br>
><br>
</div></div></blockquote></div><br>