[vtk-developers] Change semantic of VTK_DISABLE_TK_INIT

[David Cole]

Would there be any objection to a *single* new variable, VTK_USE_TK, 
which is independent of Tcl and Python and only controls Tk functionality?

Seems to me like everyone has requested the ability to "turn off Tk"...

Is there anybody out there who wants to turn Tk off for Python but on 
for Tcl in the same VTK binary tree? Or vice versa?

Or is a single switch sufficient?


Two cents, before it's too late to chime in..., :-)
David

Andy Cedilnik wrote:

>Hi Brad,
>
>Well, the option I am talking about really is both of them in one, so
>not really related to tcl or python. For example, on Cocoa, there is no
>Tk, so this option should be set to not build using Tk.
>
>Also, and this is where I really want the option, I want to have
>dashboard that does all VTK testing without DISPLAY being set.
>
>All this said, I think I would be ok with two options I need to turn OFF
>instead of one option I need to turn ON.
>
>       Andy
>
>Brad King wrote:
>
>  
>
>>Brad King wrote:
>>
>>    
>>
>>>Andy Cedilnik wrote:
>>>
>>>      
>>>
>>>>I am thinking about changing the semantic of VTK_DISABLE_TK_INIT from
>>>>whatever it is it does now to be do not build with TK. That would mean
>>>>if this option is on, then TK is not initialized, vtkTkRenderWidget and
>>>>so on are not build, and nothing is linked to TK.
>>>>
>>>>Any problem with that?
>>>>        
>>>>
>>Oops, the setting Andy is talking about has nothing to do with Python,
>>but it plays the equivalent role for Tcl.  Perhaps instead we should
>>have an option for use of Tk by each language with a consistent naming
>>convention:
>>
>>VTK_USE_TK_IN_TCL
>>VTK_USE_TK_IN_PYTHON
>>    
>>
>
>
>  
>