-
Notifications
You must be signed in to change notification settings - Fork 971
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
Extend build system comparison checks #2039
Extend build system comparison checks #2039
Conversation
armandomontanez
commented
Nov 13, 2024
- Adds check that ensures the Bazel and CMake Pico SDK version strings stay in sync.
- Adds check that ensures the Bazel pins for external dependencies stays in sync with the git submodule pins.
- Updates cyw43-driver pin in Bazel.
- Makes the checks for some build configurability options non-blocking.
* Adds check that ensures the Bazel and CMake Pico SDK version strings stay in sync. * Adds check that ensures the Bazel pins for external dependencies stays in sync with the git submodule pins. * Updates cyw43-driver pin in Bazel. * Makes the checks for some build configurability options non-blocking.
Example output:
|
"CYW43_DEFAULT_PIN_WL_CLOCK", | ||
"CYW43_DEFAULT_PIN_WL_CS", | ||
"CYW43_PIO_CLOCK_DIV_INT", | ||
"CYW43_PIO_CLOCK_DIV_FRAC", |
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.
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.
Bleh, I forgot to pull latest changes before adding these. This just squelches the warnings, the findings shouldn't get in the way of anything. I can put up a separate PR to add those.
|
||
current_submodule_pin = subprocess.run( | ||
("git", "-C", SDK_ROOT, "rev-parse", f'HEAD:lib/{maybe_match.group("dependency")}'), | ||
text=True, |
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.
I guess this is assuming that our submodules are always in the lib/
subdirectory? Whilst this will probably always be true for pico-sdk
, I guess moving the lib/
part of the path into the MODULE.bazel
file might give you an extra bit of flexibility? 🤷
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.
Sent out #2040 for this one