[MacPorts] #53131: drumstick, vmpk (virtual midi piano keyboard): new ports

[MacPorts]

#53131: drumstick, vmpk (virtual midi piano keyboard): new ports
-----------------------------+-----------------
  Reporter:  mojca           |      Owner:
      Type:  submission      |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  drumstick vmpk  |
-----------------------------+-----------------

Comment (by RJVB):

 Replying to [comment:2 mojca]:

 > I tested `drumstick-vpiano` and it seems to be crashing once I press a
 button. The

 Not for me...

 > Just curious, why does your port use the `cxx11` portgroup? I can
 imagine that this

 I must have seen a reference to C++11 somewhere. Using that PortGroup is a
 "noop" on 10.9 and up because those already use libc++ as the system C++
 runtime. You're on 10.9 too, no?

 > Without testing anything, you might perhaps have any clue why
 > {{{
 > -DQt5LinguistTools_DIR=${prefix}/libexec/qt5/lib/cmake/Qt5LinguistTools/
 > }}}
 > is needed to find `Qt5LinguistToolsConfig.cmake`. That is: why doesn't
 the qt5 PortGroup take care of finding its location or why doesn't Qt5 put
 the cmake files to a more reasonable location?

 > (Let me guess: your patches for Qt5 already fix the issue.)

 To answer that question first: yes and no. There's no need to patch Qt for
 that, just to let it install the files to a standard location, and that's
 what my port:qt5-kde does. Installing everything somewhere under libexec
 is nice and easy to avoid conflicts with other Qt ports, but makes things
 a lot more annoying for dependents. In case of Qt it isn't even necessary,
 and I had sufficient proof of that by the time Michael and mcalhoun
 started making their ports co-installable.

 Mcalhoun's Qt5 PortGroup does define `qt_cmake_module_dir` which you can
 add to CMake's CMAKE_MODULE_PATH, but even the cmake 1.1 portgroup doesn't
 provide an easy API to append elements to that path.

 That's something I should have realised before...

--
Ticket URL: <https://trac.macports.org/ticket/53131#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS