Skip to content
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

[v1.4] proto submodule update #1943

Merged
merged 4 commits into from
Jan 13, 2023
Merged

[v1.4] proto submodule update #1943

merged 4 commits into from
Jan 13, 2023

Conversation

julianoes
Copy link
Collaborator

This points to the v1.4 branch which contains the protobuf version fix.

This points to the v1.4 branch which contains the protobuf version fix.

Signed-off-by: Julian Oes <julian@oes.ch>
@julianoes julianoes added the bug label Dec 15, 2022
@julianoes
Copy link
Collaborator Author

Once this passes CI, I will release v1.4.10 and use that for a Python release, however, the branch used will be https://github.com/mavlink/MAVSDK-Proto/tree/v1.4-log-files-fix

@julianoes
Copy link
Collaborator Author

Unhappy CI, blerg.

@JonasVautherin
Copy link
Collaborator

ModuleNotFoundError: No module named 'future'

I am starting to hate this module 😆

No idea how this stuff works but it's worth a try to tame cmake on
macOS.

Signed-off-by: Julian Oes <julian@oes.ch>
Signed-off-by: Julian Oes <julian@oes.ch>
Signed-off-by: Julian Oes <julian@oes.ch>
@julianoes julianoes merged commit 301a7d7 into v1.4 Jan 13, 2023
@julianoes julianoes deleted the v1.4-proto-submodule branch January 13, 2023 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants