[MacPorts] #46853: VTK @6.1.0 +qt4 variant added
#46853: VTK @6.1.0 +qt4 variant added -------------------------+-------------------------------- Reporter: joelfred@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: vtk -------------------------+-------------------------------- Added the option to build VTK with QT4, which is needed by VisIt, a port I am in the process of creating and submitting. For discussion: should qt4 or qt5 be a default variant? Also: I have not tested the qt5 variant, but it doesn't look like it should work, since VTK needs configuration environment variables when configuring it to work with qt5. See: http://www.vtk.org/Wiki/VTK/Configure_and_Build#Qt5..2A -- Ticket URL: <https://trac.macports.org/ticket/46853> MacPorts <https://www.macports.org/> Ports system for OS X
#46853: VTK @6.1.0 +qt4 variant added --------------------------+-------------------------------- Reporter: joelfred@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vtk | --------------------------+-------------------------------- Comment (by joelfred@…): It does warn about vtk violating /opt/local/plugins, but I'm very not sure what that means. I think that's where the plugins are supposed to go, but Macports doesn't know about the ${prefix}/plugins convention so it complains? -- Ticket URL: <https://trac.macports.org/ticket/46853#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#46853: VTK @6.1.0 +qt4 variant added --------------------------+-------------------------------- Reporter: joelfred@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vtk | --------------------------+-------------------------------- Comment (by rjvbertin@…): If you add Qt support via variants, they typically need to be mutually exclusive, and this port is no exception from what I can see. -- Ticket URL: <https://trac.macports.org/ticket/46853#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#46853: VTK @6.1.0 +qt4 variant added --------------------------+-------------------------------- Reporter: joelfred@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vtk | --------------------------+-------------------------------- Comment (by rjvbertin@…): Replying to [comment:2 joelfred@…]:
It does warn about vtk violating /opt/local/plugins, but I'm very not sure what that means. I think that's where the plugins are supposed to go, but Macports doesn't know about the ${prefix}/plugins convention so it complains?
That plugin directory contains the QVTKWidgetPlugin designer plugin. To be installed correctly, `-DVTK_INSTALL_QT_DIR:PATH=${qt_plugins_dir}/designer` must be added to the configure arguments. -- Ticket URL: <https://trac.macports.org/ticket/46853#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#46853: VTK @6.1.0 +qt4 variant added --------------------------+-------------------------------- Reporter: joelfred@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vtk | --------------------------+-------------------------------- Comment (by rjvbertin@…): Promised, I'll be stopping now :) The last patch version replaces the Qt variants with Qt subports. For now all subports (vtk, vtk-qt4 and vtk-qt5) are all mutually exclusive, I don't know if it can even be otherwise. The advantage of using Qt subports is that dependents can specify the Qt version they require. With variants that would not be possible. -- Ticket URL: <https://trac.macports.org/ticket/46853#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts