[MacPorts] #50955: qwt61 does not build for variant +qt5

MacPorts noreply at macports.org
Thu Mar 24 02:44:59 PDT 2016


#50955: qwt61 does not build for variant +qt5
-------------------------------+--------------------------------
 Reporter:  benjamin.seppke@…  |      Owner:  macports-tickets@…
     Type:  defect             |     Status:  new
 Priority:  Normal             |  Milestone:
Component:  ports              |    Version:  2.3.4
 Keywords:                     |       Port:  qwt61
-------------------------------+--------------------------------
 Following Ticket #49143, which seems to have already been fixed, I
 encountered another problem for the qwt port. The build and installation
 pass for the +qt5 variant, but result in wrongly linked dylibs. This
 forces macports to rebuild qwt61 three times before giving up.

 I pinned the errors down to the librarys for qwt and the designer plugin.
 Here, the prefix path is missing for both, the lib itself and the linked
 lib (for the designer plugin). If I install the qwt61 manually from source
 using /opt/local/libexec/qt5/bin/qmake after setting:
 {{{
 QWT_INSTALL_PREFIX = QT_INSTALL_PREFIX and
 QWT_CONFIG += QwtFramework
 }}}
 in qwtconfig.pri
 I get the same wrongly linked binaries, which I am able to fix using sudo
 of:
 {{{
 #Patch qwt lib (inside framework)
 install_name_tool -id
 /opt/local/libexec/qt5/lib/qwt.framework/Versions/6/qwt
 /opt/local/libexec/qt5/lib/qwt.framework/Versions/6/qwt

 #Patch designer plugin
 install_name_tool -id
 /opt/local/libexec/qt5/plugins/designer/libqwt_designer_plugin.dylib
 /opt/local/libexec/qt5/plugins/designer/libqwt_designer_plugin.dylib
 install_name_tool -change qwt.framework/Versions/6/qwt
 /opt/local/libexec/qt5/lib/qwt.framework/Versions/6/qwt
 /opt/local/libexec/qt5/plugins/designer/libqwt_designer_plugin.dylib
 }}}

 This should probably done in the Portfile, too. Another point is, that the
 qwt-Port currently promotes header and libs to the "global"
 /opt/local/include and /opt/local/lib directories. I think, we should
 disable this behaviour and always install qwt as a framework inside the
 corresponding qt4/5 directory. This will make it possible to have qwt61
 installed for qt4 and qt5 in parallel without conflicts. All we would need
 for this is to promote the headers inside the corresponding qt
 installations. For qt5 e.g.:
 {{{
 #Promote headers
 ln -s /opt/local/libexec/qt5/lib/qwt.framework/Versions/6/Headers
 /opt/local/libexec/qt5/include/qwt
 }}}

 Maybe this defect is a good opportunity to think about not just fixing
 qwt, but really improving it.

-- 
Ticket URL: <https://trac.macports.org/ticket/50955>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list