You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2023. It is now read-only.
At the moment, we can supply our own configuration file pairs, and they are copied over the originals before a build, and it's working well.
I was thinking, it would be nice to have a way to build two (or more) firmwares at a time, to compare their results. Of course, I could do this manually by just making one then making the other, but it would be nice to only have to press the magic button once ;)
I'm hoping this might be very simple, rather than copying the file pairs before the build, it could look for directories there, and do one build for each directory it finds, with the config files from that directory.
What do you think?
The text was updated successfully, but these errors were encountered:
We can probably do both? If there are .h files in config directory, compile a single firmware bin. If there are folders there, go recursively inside each folder and build to the corresponding compiled firmware folder? 😄
Sounds great!
This project has finally put a fire under me to learn more about docker so hopefully I can contribute in future if you would like some help?
I considered modifying the script to accommodate for this, however it would increase the complexity a fair bit. Since this is a edge-case, i recommend solving it in a more static approach using Github Actions.
Create multiple GHA workflows, where you change out the monitored folders and docker volumes with sub-folders of choice. If you make changes in the sub-folder, only the corresponding firmware will be generated.
At the moment, we can supply our own configuration file pairs, and they are copied over the originals before a build, and it's working well.
I was thinking, it would be nice to have a way to build two (or more) firmwares at a time, to compare their results. Of course, I could do this manually by just making one then making the other, but it would be nice to only have to press the magic button once ;)
I'm hoping this might be very simple, rather than copying the file pairs before the build, it could look for directories there, and do one build for each directory it finds, with the config files from that directory.
What do you think?
The text was updated successfully, but these errors were encountered: