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
I've been working with zephyr-env.ps1 and noticed that the current toolchain configuration requires manually editing the script file each time we need to change toolchains. I'd like to share an enhancement idea that might improve the developer experience.
The Concept
Add command-line parameter support to zephyr-env.ps1 for dynamic toolchain configuration:
# Configure and save toolchain settings. .\zephyr-env.ps1 gnuarmemb "D:\path\to\gcc"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Zephyr community! 👋
I've been working with
zephyr-env.ps1and noticed that the current toolchain configuration requires manually editing the script file each time we need to change toolchains. I'd like to share an enhancement idea that might improve the developer experience.The Concept
Add command-line parameter support to
zephyr-env.ps1for dynamic toolchain configuration:Reload saved configuration
. .\zephyr-env.ps1
.gitignore: add TOOLCHAIN_PATH.txt:

zephyr-env.ps1.txt
Beta Was this translation helpful? Give feedback.
All reactions