chore: proof-of-concept / demo Bazel support #157
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is not intended for merging, but as a proof-of-concept / demo for parallel Bazel and vanilla-Go builds (i.e. consumers are not required to use Bazel).
Running, for example,
bazel build //cmd/geth
on this branch will produce a bit-level-identical reproducible build. This can be extended withrules_oci
to build Docker images in a similar fashion.All
BUILD.bazel
files except for thegazelle()
targets in the root directory's build file are auto-generated bybazel run //:gazelle
so the only files of interest are (a)MODULE.bazel
and (b) the patches inlibevm/internal/bazel
to help thegazelle
auto-generation whencgo
confuses it.There are a few failing tests due to different directory access, which I haven't bothered fixing.