Changes between Initial Version and Version 1 of Ticket #67672, comment 11


Ignore:
Timestamp:
Jun 29, 2023, 3:42:26 PM (11 months ago)
Author:
kaamui
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #67672, comment 11

    initial v1  
    33Thanks 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.
    44
    5 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.
     5I 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 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.
    66
    77I'll update my answer if anything new comes out from my tests