Some confusion here trying to use Fedora's Qt 5 packages, and it seems they cannot be use quickly. $ rpm -qa qt5\*|sort qt5-qtbase-5.3.2-3.fc21.x86_64 qt5-qtbase-devel-5.3.2-3.fc21.x86_64 qt5-qtbase-gui-5.3.2-3.fc21.x86_64 qt5-qtbase-ibase-5.3.2-3.fc21.x86_64 qt5-qtbase-mysql-5.3.2-3.fc21.x86_64 qt5-qtbase-odbc-5.3.2-3.fc21.x86_64 qt5-qtbase-postgresql-5.3.2-3.fc21.x86_64 qt5-qtbase-tds-5.3.2-3.fc21.x86_64 No "moc" in PATH, no "uic" either. Just moc-qt5 and uic-qt5. $ pkg-config --variable=moc Qt5 /usr/lib64/qt5/bin/moc $ pkg-config --variable=uic Qt5 $ $ rpm -qf /usr/lib64/qt5/bin/moc qt5-qtbase-devel-5.3.2-3.fc21.x86_64 No documentation in that package: $ rpm -qd qt5-qtbase-devel $ It seems to be specific to Fedora. Looking up the qt5-qtbase spec file, even the Qt5.pc file is generated there. The "moc" variable is added there to help finding MOC, but why not also UIC? All binaries get renamed to avoid a conflict, but I couldn't find a helper script to make them available in path again. I think of a shell file in a fixed location one could source. And why isn't any of this documented in the package description? It looks like one could simply prepend /usr/lib64/qt5/bin to $PATH to make available the executables, which are renamed to avoid conflicts with other Qt versions. $ rpm -qi qt5-qtbase-devel|tail -2 Description : Development files for qt5-qtbase. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
