.qmlc and .jsc files cannot be built on !x86, breaking the packaging of
a few x11/qt5 subports on these archs. We're introducing here
MODQT5_COMMENT in a similar way to what python does with MODPY_COMMENT.
Tested on macppc amd amd64. Hints by George Koehler and landry@,
proposed by sthen@ (thanks you all!), applied by me.
OK landry@ rsadowski@
Tested with both GCC and CLang (less through).
This forces updating x11/py-qt5, which forces update of devel/py-sip,
which forces update of x11/py-qt4, but, thankfully, no breakage detected.
This removes support of separate qmake versions in one port: as we
discovered, there are no ports actually needing this; strangers like
print/poppler don't use qmake in build.
This should be transparent to current ports. But expect more tweaks there:
for now, qt?.port.mk forces qmake.port.mk inclusion, but that will be
reworked to a more common scheme.
Same idea from (at least) espie@ and me; also, espie@ agrees on the plan.
an opt-in. Actual qmake-based ports will be switched on case-by-case
basis in the near future.
Unslacking after discussion with at least naddy@ & espie@ from... 2014?!
Oh my.
CMake files are not installed in ${PREFIX}/lib anymore; instead,
the qt5.port.mk will provide necessary environment variables to help
CMake to find the Qt5 packages.
Not connected to build, so no bump.
Qt is a full development framework with tools designed to streamline
the creation of applications and user interfaces for desktop,
embedded, and mobile platforms.
This port is not enabled yet, because some ports will pick up Qt5
instead of Qt4, breaking build. Those will be fixed separately soon.
There are some non-critical things left to do:
1. Support for OpenBSD sensors framework.
2. V4L2 support.
3. -L${LOCALBASE}/* could come before -L${WRKBUILD}/* when linking is
done across Qt module boundaries. This means that builds of Qt 5.y
while having Qt 5.x installed (x < y) will be busted.
Volunteers are welcome to come in and help fixing those problems.
Last note: don't even try to build "debug" FLAVOR unless you know
what you're doing and you have about 20GB of free space. You've
been warned.
landry@ agrees on continuing working in-tree
