Context Navigation

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

initial	v1
7	7	After rereading your comments, I understand now that the problem here isn't that the linkages of your app and the libraries/frameworks weren't edited properly (they were); the problem is that the QtWebEngineCore framework contains a QtWebEngineProcess app, and this QtWebEngineProcess app's linkage hasn't been edited. The stackoverflow post you referred to said the same issue was seen when Qt was installed by Homebrew. This sounds like a bug in `macdeployqt`. Until it is fixed, you should be able to edit QtWebEngineProcess's linkage manually using `install_name_tool`.
8	8
9		I understand that the official Qt binary distribution doesn't have this issue. It is built using `@rpath`. Using `@rpath` causes some problems so in MacPorts we've decided not to ship libraries that use `@rpath`. The bug may be that `macdeployqt` expects ~~things to be~~ built with `@rpath`.
	9	I understand that the official Qt binary distribution doesn't have this issue. It is built using `@rpath`. Using `@rpath` causes some problems so in MacPorts we've decided not to ship libraries that use `@rpath`. The bug may be that `macdeployqt` expects Qt to have been built with `@rpath`.
10	10
11	11	Searching the [https://bugreports.qt.io Qt bug tracker] for "macdeployqt" I found [https://bugreports.qt.io/browse/QTBUG-84200 bug 84200] which seems to describe the problem exactly. They closed it as not their problem, referring the user back to Homebrew; I disagree with that conclusion.