Skip to content

Always generate exactly one toolchain #132

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

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

mering
Copy link
Contributor

@mering mering commented Jan 8, 2025

Improvements after #130. This makes sure that there is always exactly one toolchain defined, either in the root module or picking the default one.

@mering mering force-pushed the module-extension-fixes branch from 2cfbefa to 515b1b1 Compare January 8, 2025 16:56
@mering mering changed the title Minor fixes after #130 Always generate exactly one toolchain Jan 8, 2025
@mering mering force-pushed the module-extension-fixes branch from 515b1b1 to 0f87641 Compare January 8, 2025 16:58
@mering mering force-pushed the module-extension-fixes branch from 0f87641 to aef8dec Compare January 8, 2025 16:59
@Ongy
Copy link

Ongy commented Jan 23, 2025

@abrisco did you get a chance to look at this? Then I can rebase my PR.

@abrisco abrisco merged commit ae59209 into abrisco:main Jan 23, 2025
8 checks passed
Copy link
Owner

@abrisco abrisco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@mering mering deleted the module-extension-fixes branch January 24, 2025 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants