Skip to content

refactor: migrate to rules based toolchain #497

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

thesayyn
Copy link

WIP, #444

@thesayyn thesayyn force-pushed the rules_based_toolchain branch from 4248bd4 to f0ef928 Compare May 13, 2025 19:20
@fmeum
Copy link
Member

fmeum commented Jun 13, 2025

@thesayyn Sorry, I forgot about this. Is this ready for review?

@thesayyn
Copy link
Author

@fmeum its not close to being done, but i'd really appreciate the early feedback here. I am committed to land this and some more.

@fmeum
Copy link
Member

fmeum commented Jun 29, 2025

@thesayyn Took me a while not the general approach looks good to me.

I like to see a workaround for bazelbuild/rules_cc#277 - have you tried to upstream it?

This repo currently reuses the toolchain config from rules_cc. Is your plan to no longer do this or to also migrate the default toolchain to the new rules? Either would be fine, just curious.

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.

2 participants