Skip to content

Conversation

qobilidop
Copy link
Member

The explicit rules_cc usage is causing some trouble building things internally at Google. So we want to use this temporary hack to unblock some internal work. We only need a commit to refer to. So this PR is not intended to be merged. I'll close this PR once the hack is no longer needed.

@qobilidop qobilidop force-pushed the temp-remove-rules-cc branch 2 times, most recently from 9493daa to e0b49f7 Compare September 15, 2025 15:40
@qobilidop
Copy link
Member Author

@Shoooooon I think this might be easier to maintain on top of HEAD than creating a separate feature branch as proposed in #176.

@Shoooooon
Copy link
Contributor

Shoooooon commented Sep 15, 2025

@Shoooooon I think this might be easier to maintain on top of HEAD than creating a separate feature branch as proposed in #176.

I agree -- having a commit to refer to is sufficient.

Signed-off-by: Bili Dong <[email protected]>
@qobilidop qobilidop force-pushed the temp-remove-rules-cc branch 14 times, most recently from b31aea6 to 21b1bae Compare September 16, 2025 00:11
Signed-off-by: Bili Dong <[email protected]>
@qobilidop qobilidop changed the title [DO NOT MERGE] Remove rules_cc [DO NOT MERGE] Remove rules_cc and fix builds for Google internal projects Sep 16, 2025
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