Here is a working (but to be polished, of course) port of Qt 5. It's based on x11/qt4 from CVS, but have the following advantages:
1. Using more common spread suffixes for programs ("-qt5" vs. plain "5").
2. More upstream-friendly patches for qmake. I'll try to push them
upstream if they will be justified to be okay for us.
Disadvantages:
1. Recent GCC required. CLang doesn't work due to bugs in our binutils.
2. No docs due to qdoc segfault. Too hard to debug due to same reasons
as above. Yes, GDB doesn't work.
Things still left to do (non-critical, IMHO, but still):
1. Support for OpenBSD sensors framework.
2. V4L2 support (look at the fswebcam for patched videodev2.h?).
3. -L/usr/local/* 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.
I've tested the port on net/transmission,-qt - things work fine for
now. Any additional feedback is welcome, of course. Especially on
non-x86 platforms.
I propose adding the port to CVS unlinked now, to make it easier spot
and adjust ports that try Qt5 before Qt4 (like Transmission does).
After that, Qt5 could be linked in. I hope this will be done before
5.7 freeze, so KDE5 porting could start right after tagging release.
So... comments? okays? Thanks in advance. :)
--
WBR,
Vadim Zhukov
P.S.: 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.
qt5-5.3.2_port.tar.gz
Description: GNU Zip compressed data
