-
-
Notifications
You must be signed in to change notification settings - Fork 599
Move to cpp folder #2763
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
Move to cpp folder #2763
Conversation
f0f78e7 to
1ffc9da
Compare
1ffc9da to
f146cb8
Compare
f146cb8 to
26956f8
Compare
08ced34 to
f6321a3
Compare
403fd14 to
ef788f7
Compare
|
@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. |
julianoes
left a comment
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.
Nice! I like folders.
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 |
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.
Whoops. Thanks.
Let's see what the CI says...
Makes it look like this: