Skip to content

Conversation

@JonasVautherin
Copy link
Collaborator

@JonasVautherin JonasVautherin commented Feb 5, 2026

Let's see what the CI says...

Makes it look like this:

Screenshot 2026-02-06 at 00 34 27

@JonasVautherin JonasVautherin force-pushed the move-to-cpp-folder branch 3 times, most recently from f0f78e7 to 1ffc9da Compare February 5, 2026 23:44
@JonasVautherin JonasVautherin removed the request for review from julianoes February 5, 2026 23:53
@mavlink mavlink deleted a comment from sonarqubecloud bot Feb 6, 2026
@julianoes
Copy link
Collaborator

julianoes commented Feb 7, 2026

@JonasVautherin this will probably be MAVSDK v4 when it merges, right?

I mean technically it might not have to, but it feels like it could.

Copy link
Collaborator

@julianoes julianoes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! I like folders.

@JonasVautherin
Copy link
Collaborator Author

this will probably be MAVSDK v4 when it merges, right?

IMO the major version of a library should indicate if it will break the build or not. This just moves the projects into a subfolder, but the resulting compiled library should be exactly the same; it should not break the build of anyone.

By bumping to v4, my concern would be that some people may not update because they don't want to fix compilation issues...

[submodule "mavsdk-proto"]
path = proto
url = https://github.com/ryanf55/MAVSDK-Proto.git
url = https://github.com/mavlink/MAVSDK-Proto.git
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops. Thanks.

@julianoes julianoes merged commit ef29d2e into main Feb 8, 2026
55 checks passed
@julianoes julianoes deleted the move-to-cpp-folder branch February 8, 2026 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants