-
Notifications
You must be signed in to change notification settings - Fork 33
Add an option for custom toolchain and interactive toolchain selection #268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
hide generic toolchains for xtensa fmt
SergioGasquez
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this! Just left some comments, maybe we should have a toolchain module as we have quite a lot of logic for it.
|
@SergioGasquez, I agree with a separate module part, done |
MabezDev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
bjoernQ
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM


closes #250
I've created a new category for the
tuitemplate with a placeholder option, which then will be replaced by installed toolchains.Toolchain list in the TUI is auto-populated from installed rustup toolchains that actually support the selected chip target and current MSRV of a template project
The
Toolchain:label in the TUI header shows either the user’s chosen toolchain or that template defaults will be used, this is how workflow works too; if user selected different toolchain in the TUI or via--toolchainparameter - selected one will be used, otherwise template defaults fromrust-toolchain.yamlcompress-demo.mp4