Skip to content
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

Document cc_configure #8786

Open
hlopko opened this issue Jul 3, 2019 · 1 comment
Open

Document cc_configure #8786

hlopko opened this issue Jul 3, 2019 · 1 comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-CPP Issues for C++ rules type: documentation (cleanup)

Comments

@hlopko
Copy link
Member

hlopko commented Jul 3, 2019

C++ toolchain autoconfiguration (cc_configure) is quite powerful and customizable, as well as quite undocumented. Pls document its existence and all env variables that customize it (most notably CC, BAZEL_CXXOPTS, BAZEL_LINKOPTS, BAZEL_LINKLIBS).

@hlopko hlopko added type: documentation (cleanup) P2 We'll consider working on this in future. (Assignee optional) team-Rules-CPP Issues for C++ rules bazel 1.0 labels Jul 3, 2019
@hlopko hlopko self-assigned this Jul 3, 2019
@dslomov dslomov removed the bazel 1.0 label Jul 24, 2019
@oquenchil oquenchil added P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed P2 We'll consider working on this in future. (Assignee optional) P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) labels Nov 19, 2020
@sgowroji sgowroji added the team-Documentation Documentation improvements that cannot be directly linked to other team labels label Jan 11, 2023
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-CPP Issues for C++ rules type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

4 participants