-
Notifications
You must be signed in to change notification settings - Fork 56
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
CheckProjectStatus is too restrictive #33
Comments
This is a patch for the build scripts that breaks error detection but alllows to build Qt and nymea. Make sure to verify build results yourself from the logs if using those patches as actual errors might go unnoticed. IMO the packagescripts need to be fixed to fail on bad exit code from the build/install scripts, but not care about their actual printed output. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to build some more complex projects and generally I'm getting through, but I've got some builds failing because of CheckProjectStatus being too restrictive.
There are build scripts which test stuff and cause error messages in the log but those errors are not critical. Still the tools fails on those.
Commenting the call out in include/build gets me past this.
The text was updated successfully, but these errors were encountered: