[MacPorts] #39424: Ports that use qmake: consider using the new qmake portgroup

[MacPorts]

#39424: Ports that use qmake: consider using the new qmake portgroup
-------------------------------------------------+-------------------------
  Reporter:  egall@…                             |      Owner:  macports-
      Type:  enhancement                         |  tickets@…
  Priority:  Normal                              |     Status:  new
 Component:  ports                               |  Milestone:
Resolution:                                      |    Version:  2.1.3
      Port:  abtransfers arora bitcoin bitdht    |   Keywords:
  clustalx cmake djview doxygen GLC_lib          |
  gnuradio goldendict k3dsurf kdiff3             |
  libQGLViewer OpenCSG openscad psi-otr py-      |
  pyqt4 py26-pyqt3 qca qfsm qgit QMK-            |
  Groundstation qscintilla qt-assistant qt3      |
  qt3-mac qt4-creator-mac qt4-mac qt4-mac-       |
  mysql55-plugin qt4-mac-postgresql91-plugin     |
  qt4-mac-sqlite2-plugin qt4-x11 qtc-qtsharp     |
  qtiplot qtpfsgui qtscriptgenerator qtsharp     |
  QupZilla qwt qwtplot3d qxmpp sqlitedbrowser    |
  tea texstudio tiled Vidalia x2goclient xxdiff  |
-------------------------------------------------+-------------------------

Comment (by nicos@…):

 Sorry I did not answer right away.

 If I did put those in a pre-configure block, it is because otherwise, the
 flags were not set right if the portfile was for example setting
 `configure.blacklist`, as flags such as QMAKE_CC must be set accordingly,
 and after having blacklisted compilers. This is also why all flags are
 with `-delete` or `-append`.
 However, I fully get the point, and if there is another more convenient
 way of ensuring that some commands are followed that I am not aware of, it
 surely could improve the portgroup.

-- 
Ticket URL: <https://trac.macports.org/ticket/39424#comment:17>
MacPorts <http://www.macports.org/>
Ports system for OS X