[MacPorts] #67672: qt5-qtbase @5.15.8: macdeployqt doesn't fix QtWebEngineProcess
MacPorts
noreply at macports.org
Thu Jun 29 10:18:33 UTC 2023
#67672: qt5-qtbase @5.15.8: macdeployqt doesn't fix QtWebEngineProcess
----------------------------------+---------------------------------
Reporter: kaamui | Owner: MarcusCalhoun-Lopez
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: qt5 qt5-qtwebengine |
----------------------------------+---------------------------------
Comment (by kaamui):
Sorry for the late reply. Sadly, I already had tested it before I created
this ticket. It doesn't help with recent Qt 5. I also tried to manually
fix absolute paths with relative one, but as explained by the user on the
SO thread, it just move the issue to the libs that are no longer able to
find their own dependencies.
Thanks for the good and precise explanation, it helps understanding the
whole issue. I saw your comment on the closed Qt bug. I think we'll have
to open a new Bug if you want to obtain Qt's attention on it.
I compiled webengine myself, both using official Qt binaries, and macports
ones, and even if my tests aren't completely finished (testing with both
Qt 6 and Qt 5, on intel and arm (only Qt 6 for arm, because Qt doesn't
provide official Qt 5.15 packages on arm), with or without universal), I
can confirm I obtained the expected result at this point :
QtWebEngineProcess links refer to its dependencies with relative paths
when compiled with official Qt 5.15.2, and with absolute paths when using
MacPorts Qt. WebEngine then only works when compiled with Official Qt.
I'll update my answer if anything new comes out from my tests
--
Ticket URL: <https://trac.macports.org/ticket/67672#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list