Skip to content

chore: proof-of-concept / demo Bazel support #157

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Conversation

ARR4N
Copy link
Collaborator

@ARR4N ARR4N commented Feb 28, 2025

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 with rules_oci to build Docker images in a similar fashion.

All BUILD.bazel files except for the gazelle() targets in the root directory's build file are auto-generated by bazel run //:gazelle so the only files of interest are (a) MODULE.bazel and (b) the patches in libevm/internal/bazel to help the gazelle auto-generation when cgo confuses it.

There are a few failing tests due to different directory access, which I haven't bothered fixing.

@ARR4N ARR4N added the Status: 🔴 DO NOT MERGE This PR is not meant to be merged in its current state label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: 🔴 DO NOT MERGE This PR is not meant to be merged in its current state
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant