←back to thread

700 points elipsitz | 1 comments | | HN request time: 0.245s | source
Show context
kaycebasques ◴[] No.41196104[source]
Big day for my team (Pigweed)! Some of our work got mentioned in the main RP2350/Pico2 announcement [1] but for many months we've been working on a new end-to-end SDK [2] built on top of Bazel [3] with support for both RP2040 and RP2350, including upstreaming Bazel support to the Pico SDK. Our new "Tour of Pigweed" [4] shows a bunch of Pigweed features working together in a single codebase, e.g. hermetic builds, on-device unit tests, RPC-centric comms, factory-at-your-desk testing, etc. We're over in our Discord [5] if you've got any questions

[1] https://www.raspberrypi.com/news/raspberry-pi-pico-2-our-new...

[2] https://opensource.googleblog.com/2024/08/introducing-pigwee...

[3] https://blog.bazel.build/2024/08/08/bazel-for-embedded.html

[4] https://pigweed.dev/docs/showcases/sense/

[5] https://discord.gg/M9NSeTA

replies(3): >>41196123 #>>41198567 #>>41200181 #
dheera ◴[] No.41196123[source]
I hate Bazel. A build system for C/C++ should not require a Java JVM. Please keep Java out of microcontroller ecosystem please -__--
replies(5): >>41196174 #>>41196761 #>>41196950 #>>41199461 #>>41208253 #
1. TickleSteve ◴[] No.41199461[source]
I have to admit, Bazel as a build system would mean it wouldnt even be considered by me, it has to fit in with everything else which typically means Makefiles, like it or not.

TBH, Java + Bazel + Discord makes it seem like its out of step with the embedded world.