[Bazel] Add bzl_library targets #2709

Open

RyanDraves wants to merge 1 commit from RyanDraves/develop into develop

RyanDraves commented

2025-10-28 23:59:52 -05:00

(Migrated from github.com)

Add some bzl_library targets for .bzl files. This enables stardoc to do its thing and is helpful in its own right for validating rule & macro dependencies.

Notes:

Open question: should this PR add bzl_library targets for all .bzl files? I added the ones I personally depend on, but adding it for more files requires bumping the rules_cc version; might be poking the bear?
I haven't filed an issue yet, will do as desired

Add some `bzl_library` targets for `.bzl` files. This enables [stardoc to do its thing](https://blog.aspect.build/stardocs-on-bcr) and is helpful in its own right for validating rule & macro dependencies. Notes: - Open question: should this PR add bzl_library targets for all `.bzl` files? I added the ones I personally depend on, but adding it for more files requires bumping the `rules_cc` version; might be poking the bear? - I haven't filed an issue yet, will do as desired

kilograham commented

2026-01-05 11:24:51 -06:00

(Migrated from github.com)

cc @armandomontanez

armandomontanez commented

2026-01-13 18:15:46 -06:00

(Migrated from github.com)

Bumping rules_cc should be fine.

I should probably take a pass at some of the .bzl libraries and re-assess their intended visibility. For example, configurable_feature was an implementation detail to make it easier to write/maintain the toolchains. I don't think it should be considered part of the public interface.

Btw, thanks for kicking this off, stardoc in the BCR is very cool.

Bumping rules_cc should be fine. I should probably take a pass at some of the .bzl libraries and re-assess their intended visibility. For example, `configurable_feature` was an implementation detail to make it easier to write/maintain the toolchains. I don't think it should be considered part of the public interface. Btw, thanks for kicking this off, stardoc in the BCR is very cool.

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin 'RyanDraves/develop:RyanDraves/develop'

git switch 'RyanDraves/develop'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'develop'

git merge --no-ff 'RyanDraves/develop'

git switch 'RyanDraves/develop'

git rebase 'develop'

git switch 'develop'

git merge --ff-only 'RyanDraves/develop'

git switch 'RyanDraves/develop'

git rebase 'develop'

git switch 'develop'

git merge --no-ff 'RyanDraves/develop'

git switch 'develop'

git merge --squash 'RyanDraves/develop'