-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
LMMS won't launch on OS X #2862
Comments
This is getting stranger by the day... So with 47b3378, I finally have Qt linking properly (even the 3rd party utility seems to miss the The exact error is:
But what's really happening is It appears How important is Jack support on Apple? |
I might be able to help out with testing this - I have asccess to a Mac machine but it runs OS X 10.7.5 (not the newest) and can't run homebrew. But I installed stable LMMS and it was working (apart from ZynAddSubFX). |
Thanks @unfa. In this case, the help I need is packaging and I'm not sure we have a whole lot of Mac developers on this forum to assist. In the case of my latest DMG, it installs This process is done largely in part with a utility called |
Ok, I reverted to Qt 5.5 (versus the default Qt 5.6.1) and at a glance, things are looking much better. To do this with Homebrew, I had to replace the I'll do some more testing and report results here. |
Confirmed, Qt 5.5 fixes things... @unfa here you are: https://github.com/tresf/lmms/releases/tag/v1.1.91 I'll just have to change my own build/package procedures to use Qt55. I'll sanitize the build process against the older-but-working Qt version. |
Instead of defaulting to Qt 5.6+ per LMMS#2862
Updated tutorial to reflect Qt 5.5. Closing as this is not our bug. Left the details in |
Instead of defaulting to Qt 5.6+ per LMMS#2862
Latest master branch with #2861 applied, I can get a reliable
.dmg
file, however there seems to be something wrong with theQtWidgets
library within the bundle.The error is:
What appears to be happening is the
macdeployqt
command isn't changing Qt's own references from static libraries to relative paths as can be observed by the Homebrew path prefix in the error log.At a glance it looks very similar to these bugs:
Homebrew/legacy-homebrew#42191
https://bugreports.qt.io/browse/QTBUG-47868
http://stackoverflow.com/a/18499762/3196753
https://bugreports.qt.io/browse/QTBUG-53533
https://bugreports.qt.io/browse/QTBUG-56814
https://bugreports.qt.io/browse/QTBUG-54086
Whether this is upstream or not, this completely breaks loading on Apple, so we may have to employ a workaround.
One possible workaround is to hard-code some Qt 5.6-specific
install_name_tool
commands into the end of our apple bundler script, which I consider a last-resort.Thoughts welcome.
The text was updated successfully, but these errors were encountered: