On 10/04/2015 09:53 AM, Mathieu Pellerin wrote: > > Larry, Matthias, is there an easy fix that can be applied so 2.12 can > ship and be qt5-compatible? > Can you check this and report back:
https://github.com/qgis/QGIS/pull/2347 > Oh btw, ubuntu now has qt5 packages for scintilla, qwt, and qca but > the cmake process picks the qt4 versions when cmaking with enable_qt5 > Can you confirm the first call to cmake on an empty build directory already included the ENABLE_QT5 directive? Matthias > > M > > On 4 Oct 2015 14:43, "Matthias Kuhn" <matth...@opengis.ch > <mailto:matth...@opengis.ch>> wrote: > > Hi Mathieu, > > On 10/04/2015 03:55 AM, Mathieu Pellerin wrote: >> Greetings, >> >> (Note: it's the first time I'm trying to compile QGIS using Qt5, >> so the problem might be the user here ;) ) >> >> Using the current master (what will become 2.12), I fail to >> successfully compile a build using Qt5 libraries. The make >> process crashes when trying to compile qgsauthcertutils.cpp with >> the following error: >> >> /home/webmaster/dev/cpp/QGIS/src/core/auth/qgsauthcertutils.cpp: >> In static member function ‘static QMap<QString, >> QList<QSslCertificate> > >> QgsAuthCertUtils::certsGroupedByOrg(QList<QSslCertificate>)’: >> /home/webmaster/dev/cpp/QGIS/src/core/auth/qgsauthcertutils.cpp:64:68: >> error: no matching function for call to >> ‘QString::QString(QStringList)’ >> QString org( cert.subjectInfo( QSslCertificate::Organization >> ) ); >> ^ >> In file included from >> /usr/include/x86_64-linux-gnu/qt5/QtCore/QString:1:0, >> from /usr/include/Qca-qt5/QtCrypto/qca_core.h:36, >> from /usr/include/Qca-qt5/QtCrypto/qca.h:36, >> from /usr/include/Qca-qt5/QtCrypto/QtCrypto:1, >> from >> /home/webmaster/dev/cpp/QGIS/src/core/auth/qgsauthcertutils.h:21, >> from >> /home/webmaster/dev/cpp/QGIS/src/core/auth/qgsauthcertutils.cpp:17: >> >> >> Question: is it the case that ATM master does not compile using >> Qt5 anymore? Or is there something I'm missing here? > > Yes, it looks like the authentication system is incompatible with > Qt5. In particular this API change: > > > QSslCertificate::subjectInfo() and QSslCertificate::issuerInfo() > now return a QStringList instead of a QString > > > It's pretty common for a certificate to contain more than entry > of a specific type, but in Qt 4 the API only let you access the > first one. > > https://blogs.kde.org/2012/04/14/whats-new-qt-5-ssl > > Cheers > Matthias > >> >> Thanks for the help. >> >> Math >> >> P.S. the reason why I'm trying to get a functioning Qt5-based >> build is that I've ran into a problem with Burmese character >> encoding that's fixed under Qt5, due to its use of harfbuzz-ng. >> So, one additional motivation to to the upgrade eventually :) >> >> >> _______________________________________________ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> <mailto:Qgis-developer@lists.osgeo.org> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists.osgeo.org> > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer