[bazel] use patched python rules and build wheels cache #28
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 repository is brought in as a Bazel dependency in the OpenTitan
project. In order to support offline (air-gapped) Bazel builds of
OpenTitan, all dependencies must also build in an air-gapped
environment. Since this repository make use of the Bazel Python rules,
Bazel will try to fetch and install Python packages using pip, will not
not cache them in Bazel's repository cache (as Bazel has no knowledge of
pip).
Therefore a similar approach to lowRISC/opentitan:#12091 must be taken:
that is, a custom repository rule must be added to cache Python wheels,
so that Bazel will not attempt to fetch them in the airgapped
environment if they are already present.
This partially addresses lowRISC/opentitan:#12538.
Signed-off-by: Timothy Trippel [email protected]