-
Notifications
You must be signed in to change notification settings - Fork 669
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
[OS X] Improve macdeployqt.py #5447
Comments
Can you find out what the exact cause is? |
@guruz Here's the full console log from the CI. My gut says it returned a 0 since those were considered warnings, then generated a You can replicate by switching the branch to #5340 and the Qt version to |
We should just use the official macdeployqt if the one we have is incomplete/buggy. Back at the beginning it was still unreliable and I think that's why we rolled out our own. I almost did it for the 5.6 update but I managed to fix the script easily so it wasn't worth it. |
No longer used |
Yesterday, while trying some custom builds with old changes over the CI, using
qt5.6.2
instead ofqt5.4.0
made this happen:So most of Qt libraries weren't included on a small and broken
.pkg
while the build was marked as successful on Jenkins. These kind of problems should be considered errors, not warnings, and therefore make the deploy script and CI job fail.I know this had to do with the changes in the dependencies that doesn't happen that often, but better safe than sorry.
The text was updated successfully, but these errors were encountered: