.bazelrc

# yosys 0.64 is not yet in BCR; add the unmerged PR's fork as a fallback
# registry until bazelbuild/bazel-central-registry#8862 lands.  BCR is
# listed first so all other modules resolve from the official source;
# the fork is only consulted for modules/versions BCR doesn't carry yet.
# The commit hash makes the fork reference immutable.  Mirrors what
# bazel-orfs/.bazelrc does upstream — ORFS root has its own .bazelrc so
# the upstream lines don't propagate automatically.
common --registry=https://bcr.bazel.build/
common --registry=https://raw.githubusercontent.com/oharboe/bazel-central-registry/0586b398db6edd245da97cbec29e26c5e2a808d7/

build --incompatible_strict_action_env
build --cxxopt "-std=c++20" --host_cxxopt "-std=c++20"

# Refuse to autodetect a local C++ toolchain (/usr/bin/gcc); the hermetic
# toolchain must win resolution. Mirrors tools/OpenROAD/.bazelrc.
common --repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

# Launch py_binary via a shell stub instead of rules_python's legacy python
# stub, whose '#!/usr/bin/env python3' shebang needs a host python3 before
# the hermetic interpreter takes over. Mirrors tools/OpenROAD/.bazelrc.
common --@rules_python//python/config_settings:bootstrap_impl=script

# Don't track MODULE.bazel.lock.  Resolved versions ride along with the
# pinned BCR + git_override(commit=…) coordinates in MODULE.bazel and
# downstream cache hits are what we actually care about.  Tracking the
# lockfile just means every bazel-orfs / yosys / openroad bump produces
# a 1000-line lock diff that buries the real change.  Matches what
# bazel-orfs itself does (its own .bazelrc:7).
common --lockfile_mode=off

try-import %workspace%/user.bazelrc