Closed puddly closed 11 months ago
a posted in the other PR, I think its better to patch the slc launcher. This has been tested!
https://github.com/darkxst/silabs-firmware-builder/commit/a2dcffbd0b32fba6276ce61d1e93949730d2e246
a posted in the other PR, I think its better to patch the slc launcher. This has been tested!
Hm, I kinda like this fix as we don't have to revert later on :smile:
Next time we touch this part we can still revert back to relative path, if we wish so.
I though it was nice to keep the container compatible with past behaviour, but then I guess are probably very few if any people using the container for other builds!
I though it was nice to keep the container compatible with past behaviour, but then I guess are probably very few if any people using the container for other builds!
Good argument.
FWIW, I realized that the build without fix actually run through. So maybe the SLC CLI version on SiLabs servers is already fixed?
https://github.com/NabuCasa/silabs-firmware-builder/actions/runs/5712477875
I only realized after merging this already :sweat:
So maybe the SLC CLI version on SiLabs servers is already fixed?
Yes it has been fixed already with the latest download.
Fixes #27.
(Currently untested)