[vtk-developers] GUISupport in vtkRendering

David Gobbi david.gobbi at gmail.com
Wed Feb 16 17:42:12 EST 2011


An even bigger issue (one that has come up before) is that pre-built
vtk packages are now commonplace for linux distros.  That means it
must be possible to do a full VTK build with everything, and still
separate it into tidy little binary packages afterwards.

vtk
vtk-qt
vtk-tcl
python-vtk
python-vtk-qt

etcetera.

 - David


On Wed, Feb 16, 2011 at 3:24 PM, David E DeMarle
<dave.demarle at kitware.com> wrote:
> I agree that that is the correct long term solution.
>
> On Wed, Feb 16, 2011 at 5:21 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>> Fishing those classes out into a separate library seems like a better
>> solution to me, while leaving them dependent on the main VTK_USE_QT
>> setting.  People who use Qt may still want them built, but as Tom
>> said, they often won't want them to be part of libvtkRendering even if
>> they are built.
>>
>>  - David
>>
>> On Wed, Feb 16, 2011 at 3:06 PM, David E DeMarle
>> <dave.demarle at kitware.com> wrote:
>>> Why don't we just decouple the VTK_USE_QT in VTK/Rendering/CMakeLists
>>> from the higher level one?
>>>
>>> That way you can turn it on in the one kit and keep it off in Rendering.
>>>
>>> David E DeMarle
>>> Kitware, Inc.
>>> R&D Engineer
>>> 28 Corporate Drive
>>> Clifton Park, NY 12065-8662
>>> Phone: 518-371-3971 x109
>>>
>>>
>>>
>>> On Wed, Feb 16, 2011 at 4:57 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>>>> Yes, having Rendering depend on Qt is bad.  In fact, before you
>>>> mentioned it, I didn't even know this was the case.  Following what
>>>> Berk said, the library should be called "vtkQt" instead of "vtkQtGUI".
>>>> There's a lot more going on in Qt than just GUI.
>>>>
>>>>  - David
>>>>
>>>>
>>>> On Wed, Feb 16, 2011 at 2:52 PM, Berk Geveci <berk.geveci at kitware.com> wrote:
>>>>> Hi Tom,
>>>>>
>>>>> We started (well, sort of) a project aimed at restructuring VTK for
>>>>> the purpose of better modularization. This would definitely be one of
>>>>> the things to address there. One of my objectives is to get rid of
>>>>> changes to library contents based on configuration options. In my
>>>>> opinion, if I turn on an option, I should get a new library rather
>>>>> than an existing library with more classes. Btw, I suspect that the Qt
>>>>> dependency in Rendering is for font rendering so I don't think that
>>>>> libvtkGUI would be appropriate.
>>>>>
>>>>> -ber
>>>>>
>>>>> On Wed, Feb 16, 2011 at 4:43 PM, tom fogal <tfogal at sci.utah.edu> wrote:
>>>>>> We were investigating switching to the Qt stuff in GUISupport/ instead
>>>>>> of some no-longer-maintained code that we hack every now and again to
>>>>>> keep working.
>>>>>>
>>>>>> However it seems when one enables this, Qt gets linked into
>>>>>> libvtkRendering.so.  We have some programs that do rendering without a
>>>>>> GUI, and we are not willing to link in Qt or even have it as a build
>>>>>> dependency for that part of our software.
>>>>>>
>>>>>> Any thoughts on a `libvtkGUI.so' or similar library?
>>>>>>
>>>>>> -tom
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>>>
>>>>
>>>
>>
>



More information about the vtk-developers mailing list