Attach binaries into Releases

[bmorcelli]

This Workflow runs automatically after you create a new relase.

It builds ICENAV_BOARD, TDECK_ESP32S3, "ELECROW_ESP32, MAKERF_ESP32S3 and T4_S3 environments in parallel, and if them all build successfully, it uploads to the reffered release.

with it I can add IceNav into Launcher listing and you don't need to worry with it.

Related Issues:
bmorcelli/Launcher#272
#335

[jgauchia]

Well , good, but pin definition, sensors available, etc?
Maybe not all boards have the same sensors .
Now I'm working in Waveshare ESP32P4 boards with fixed gpio, when I've finished it I'll try it

[bmorcelli]

Yeah, they usually don't have.. mostly DIY boards won't have it..

But devices like T-Deck come with predefined modules and pins, no need to change, and that is my target here 😅

On the other project I manage, we have made module pinouts dynamically set, saving it on a json file on the SDCard or LittleFS "spiffs" partition..

so users can customize it and use the pinouts available on their board at runtime, without recompiling it (which can take several minutes)

Here is how we do it.. just an idea 😉

[jgauchia]

Yeah, I'll check-it

Maybe I'll take your Idea in my project for the next release (If isn't any problem for you)

[bmorcelli]

No problem at all..

opensourcing means evolving with other devs examples 😉