The xtask package has two subcommands: build and wrap, which allow you to build the stub for a given chip and subsequently convert it to JSON format. This completes one task outlined in #17.
I've also updated the CI workflow, mostly to prepare for the addition of the ESP32-C6 and ESP32-H2. Additionally I have added a release workflow to automatically generate and upload the JSON stubs whenever a release is created.
I've also updated the README a bit.
Even though CI is green, I've noticed that building for the ESP32-S2 results in a linker error; this is the case in main as well. I know @MabezDev was working on updating the stubs, so hopefully this resolves itself with that PR whenever it lands. Maybe we should cargo build instead of cargo check in CI to test for this in the future.
The
xtaskpackage has two subcommands: build and wrap, which allow you to build the stub for a given chip and subsequently convert it to JSON format. This completes one task outlined in #17.I've also updated the CI workflow, mostly to prepare for the addition of the ESP32-C6 and ESP32-H2. Additionally I have added a release workflow to automatically generate and upload the JSON stubs whenever a release is created.
I've also updated the README a bit.
Even though CI is green, I've noticed that building for the ESP32-S2 results in a linker error; this is the case in
mainas well. I know @MabezDev was working on updating the stubs, so hopefully this resolves itself with that PR whenever it lands. Maybe we shouldcargo buildinstead ofcargo checkin CI to test for this in the future.