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.

Sign up for GitHub

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

Jump to bottom

Add documentation for runfiles libraries #6402

Closed
laszlocsomor opened this issue Oct 16, 2018 · 3 comments
Closed

Add documentation for runfiles libraries #6402

laszlocsomor opened this issue Oct 16, 2018 · 3 comments
Labels
area-Windows Windows-specific issues and feature requests 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-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: documentation (cleanup) type: feature request

Comments

@laszlocsomor
Copy link
Contributor

Description of the problem / feature request:

Document the Runfiles Libraries (e.g. the C++ one) in the Build Encyclopedia.
@laszlocsomor laszlocsomor self-assigned this Oct 16, 2018
@laszlocsomor laszlocsomor added type: feature request type: documentation (cleanup) P2 We'll consider working on this in future. (Assignee optional) area-Windows Windows-specific issues and feature requests labels Oct 16, 2018
@laszlocsomor laszlocsomor mentioned this issue Oct 16, 2018
Closed
@laszlocsomor
Copy link
Contributor Author

This bug falls under the umbrella of the Starlark rule migration guide: #3889

@laszlocsomor laszlocsomor mentioned this issue Feb 28, 2019
Closed
@laszlocsomor laszlocsomor mentioned this issue Apr 11, 2019
Merged
@Globegitter Globegitter mentioned this issue Apr 16, 2019
Closed
@laszlocsomor laszlocsomor mentioned this issue Jul 11, 2019
Closed
@dslomov dslomov removed the bazel 1.0 label Jul 24, 2019
@philwo philwo added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Jun 15, 2020
@philwo philwo added 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) labels Dec 8, 2020
@github-actions GitHub Actions
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
@davidben davidben mentioned this issue Mar 20, 2024
Open
@github-actions GitHub Actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please post @bazelbuild/triage in a comment here and we'll take a look. Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-Windows Windows-specific issues and feature requests 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-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: documentation (cleanup) type: feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@philwo @dslomov @laszlocsomor and others