-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS/Qt6/Homebrew deployment issues #69
Comments
Oh oh I want to try to set this up! https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions But I don't think I can add secrets to this repo. Can't find the button for it (but can test it on my own fork!) |
No ball.
Looks like macdeployqt did not properly resolve |
For anyone not me or Nick: #68 seems to have solved all woes in regards to building distributable macOS bundles by using Qt's own Qt distribution. |
Sticking this here for bookmarking & reference: |
Since we have automatic deployment now, I am going to close this. |
Small update to readme with regards to #69
When running
macdeployqt
from a Qt 6 installed through Homebrew, the resulting translateLocally.app bundle still refers to libraries only installed on your system locally.macdeployqt
tries to fix all these references, but fails. This issue is about this journey, what I've found so far, and hopefully a solution that not just "just use Qt5 for now".Source macdeployqt: https://github.com/qt/qtbase/blob/f5f7f78766d62b7192b98b96bbd68dab1961e54e/src/tools/macdeployqt/shared/shared.cpp
The issue starts when
macdeployqt
starts copying the plugins into the application bundle. The Homebrew version of Qt6 is compiled with relative paths:From the original location, that path resolves to
/usr/local/Cellar/qt/6.2.0/lib
. However, macdeployqt tries to resolve this after the plugin is copied, and then this path is no longer valid. Then, this path resolves to $BUILD_DIR/lib.Current work-around I'm trying because it's too stupid to work:
ln -s $(brew --prefix qt)/lib ./lib
Experimenting in #68 with this solution.
The text was updated successfully, but these errors were encountered: