-
-
Notifications
You must be signed in to change notification settings - Fork 510
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
Cleanup #1270
Cleanup #1270
Conversation
b9e03d5
to
1705663
Compare
0697e16
to
015fffa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good to me, so I need to investigate that CI failure with the XCFramework 😅
|
||
This folder contains a few helper scripts meant to automatize some tasks such as packaging. | ||
|
||
### package_mavsdk_server_framework |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is outdated, but I'll update it in a further PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue was that the -DBUILD_BACKEND
logic was not working. I replaced it by an error, stating that BUILD_BACKEND
is obsolete, which IMO is more appropriate.
302938c
to
eb220d7
Compare
Instead just print newlines and let the OS take care of when to flush. This should save some CPU cycles waiting for the flush.
This is because it throws warnings for the grpc generated headers and I can't manage to set the SYSTEM/-isystem flag correctly for these includes.
This is not actually required and was bad practice.
We can save the CPU cycles waiting for flushing and just use newlines only instead. This way the OS should take care of flushing.
This fixes the integration tests timing out because everything locks up as we're trying to lock the mutex twice in the offboard plugin, first to lock the data as we set it and then trying to send it.
CI error unrelated, merging. Otherwise this is going to conflict. |
Best reviewed commit by commit.
Closes #1055, closes #1056.