Fixes to allow downstream project to set a different Python toolchain. - Githubissues

hdl / bazel_rules_hdl

Hardware Description Language (Verilog, VHDL, Chisel, nMigen, etc) with open tools (Yosys, Verilator, OpenROAD, etc) rules for Bazel (https://bazel.build)

Apache License 2.0

120 stars 45 forks source link

Fixes to allow downstream project to set a different Python toolchain. #334

Closed mikex-oss closed 5 months ago

mikex-oss commented 5 months ago

Currently, if a downstream project attempts to use a custom Python toolchain, passes it to bazel_rules_hdl init as instructed, and the toolchain doesn't happen to be named exactly as configured for bazel_rules_hdl itself, the initialization will fail with:

Error in path: Unable to load package for @python39_x86_64-unknown-linux-gnu//:bin/python3: The repository '@python39_x86_64-unknown-linux-gnu' could not be resolved: Repository '@python39_x86_64-unknown-linux-gnu' is not defined

These changes clean up Python toolchain and vendoring of requirements.bzl.

It also pins a Bazel version for Bazelisk (official Bazel version management), updates rules_python, and removes the dependency on pybind11.

mikesinouye commented 5 months ago

/gcbrun

mikesinouye commented 5 months ago

/gcbrun

mikesinouye commented 5 months ago

/gcbrun

mikesinouye commented 5 months ago

/gcbrun

mikex-oss commented 5 months ago

/gcbrun