[Paraview-developers] VTK_USE_X set to internal

[Marcus D. Hanwell]

I see it getting marked internal by tweaking this parameter, I will
dig into why that would cause VTK_USE_X to be changed. It is a bug,
but it may take me a little time to track down where in CMake this is
being changed.

On Thu, Jun 7, 2012 at 4:23 PM, Andy Bauer <andy.bauer at kitware.com> wrote:
> 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.
>
> Andy
>
>
> On Thu, Jun 7, 2012 at 4:01 PM, Andy Bauer <andy.bauer at kitware.com> wrote:
>>
>> 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.
>>
>> 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.
>>
>> Andy
>>
>>
>> On Thu, Jun 7, 2012 at 3:50 PM, Marcus D. Hanwell
>> <marcus.hanwell at kitware.com> wrote:
>>>
>>> On Wed, Jun 6, 2012 at 2:47 PM, Fabian, Nathan <ndfabia at sandia.gov>
>>> wrote:
>>> > In a git pull from yesterday, it appears that VTK_USE_X is being marked
>>> > internal somehow, so that I can't set it from ccmake.  I am trying to
>>> > setup OSMESA and normally I think when checking OPENGL_HAS_OSMESA, it
>>> > changes VTK_USE_X from internal to visible, but I'm not really sure
>>> > where
>>> > to look for that.
>>> >
>>> > Any help?
>>> >
>>> Why do you think VTK_USE_X is set to internal? I refactored the OS
>>> Mesa support in VTK (and hence ParaView). I just pulled ParaView
>>> master, made a clean build directory with no arguments (cmake
>>> ~/src/ParaView), and VTK_USE_X is there (in advanced) and turned ON.
>>>
>>> You can see a selection of dashboard submissions including
>>> http://open.cdash.org/buildSummary.php?buildid=2339963 on VTK that
>>> test OS Mesa each night, and they are passing. I preserved the same
>>> variables (searching MESA in the cache shows VTK_OPENGL_HAS_OSMESA
>>> etc), so that the wiki instructions continued to work.
>>>
>>> I can look into this further, but I am not aware of any CMake code
>>> making these variables internal (and in my local tests they are
>>> advanced as they have always been). I would appreciate feedback if any
>>> regressions were introduced I can get them fixed up.
>>>
>>> Thanks,
>>>
>>> Marcus
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>