PS: To be clear:
Kevin Kofler wrote:
> * in the specfile, below the patches, add:
> Patch500: qt5-qtbase-5.11.1-mkspecs.patch
Yes, this qt5-qtbase patch goes into the qt5-qtwebengine (!) specfile. The
idea is that my snippet:
> mkdir patched-mkspecs-features
creates a custom directory for patched mkspecs/features in the
qt5-qtwebengine buildroot,
> cp -a /usr/lib64/qt5/mkspecs/features/qt_module{,_headers}.prf \
> patched-mkspecs-features/
copies the original files from the RHEL qt5-qtbase mkspecs/features into the
custom directory,
> patch -p3 -d patched-mkspecs-features <%{PATCH500}
patches them,
> export QMAKEFEATURES=`pwd`/patched-mkspecs-features
and then tells QMake to use them in preference to the system-installed ones,
> and then try again.
so then you can go on building QtWebEngine, and it will hopefully succeed.
And you did NOT have to touch the system qt5-qtbase, which is off limits.
I hope this helps,
Kevin Kofler
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
