Skip to content

Commit 7c0ad2a

Browse files
committed
chore: drop what the bazel surface removal left behind
#4501 removed ORFS's MODULE.bazel and BUILD files, and c9e1ba4 the plumbing that only they referenced. These files and doc sections describe or serve that build, and nothing reads them now: flow/README.md the bazel targets of every design (<n>_synth, ..., <n>_test) and how to add a design's BUILD.bazel. Those targets and design.bzl are gone. docs/user/BuildLocally.md "Using Bazel to build OpenROAD and run the ORFS flow" runs `bazelisk run //:install_for_bazel`, a target that went with the root BUILD.bazel. "Build OpenROAD and run a few ORFS flows with Bazel" builds designs/asap7/gcd targets and bumps a MODULE.bazel, neither of which exists. bazel/install.sh its only caller was //:install_for_bazel. bazel/README.md describes flow/BUILD.bazel examples and the bazel-orfs version pin in MODULE.bazel. bazel/slang-compat/README a placeholder for when ORFS is the root module consuming tools/OpenROAD through git_override. Without a MODULE.bazel, ORFS is never the root module. flow/util/cred_helper.py a GCP credential helper for the bazel artifact repository (fabdb02); nothing references it. flow/util/open_plots.sh an xdg-open wrapper for the bazel plot_congestion target, removed in #4085 and #4096. The /bazel/ line in CODEOWNERS goes with the directory. .bazelversion and .bazelignore stay: bazelisk in docker/Dockerfile.claude reads .bazelversion. Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
1 parent 9ca2a9e commit 7c0ad2a

8 files changed

Lines changed: 0 additions & 396 deletions

File tree

‎.github/CODEOWNERS‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,6 @@
2323
/tools/AutoTuner/docker-compose.yml @The-OpenROAD-Project/openroad-devops
2424

2525
# Bazel build support.
26-
/bazel/ @The-OpenROAD-Project/openroad-devops
2726
/.bazelversion @The-OpenROAD-Project/openroad-devops
2827
/.bazelignore @The-OpenROAD-Project/openroad-devops
2928

‎bazel/README.md‎

Lines changed: 0 additions & 60 deletions
This file was deleted.

‎bazel/install.sh‎

Lines changed: 0 additions & 123 deletions
This file was deleted.

‎bazel/slang-compat/README‎

Lines changed: 0 additions & 6 deletions
This file was deleted.

‎docs/user/BuildLocally.md‎

Lines changed: 0 additions & 51 deletions
Original file line numberDiff line numberDiff line change
@@ -12,20 +12,6 @@ cd OpenROAD-flow-scripts
1212
sudo ./setup.sh
1313
```
1414

15-
## Using Bazel to build OpenROAD and run the ORFS flow (unsupported)
16-
17-
For ORFS/OpenROAD developers. Most of `./setup.sh` isn't needed when
18-
building OpenROAD with Bazel — this provides the bare minimum to build
19-
OpenROAD and test ORFS flows. No sudo required.
20-
Install [Bazelisk](https://bazel.build/install/bazelisk) first.
21-
22-
``` shell
23-
git clone --recursive https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts
24-
cd OpenROAD-flow-scripts
25-
bazelisk run //:install_for_bazel
26-
cd flow && make
27-
```
28-
2915
## Build
3016

3117
``` shell
@@ -68,40 +54,3 @@ Set up environment variables using `dev_env.sh`, then start Visual Studio Code.
6854
. ./dev_env.sh
6955
code tools/OpenROAD/
7056
```
71-
72-
## Build OpenROAD and run a few ORFS flows with Bazel
73-
74-
Local use case:
75-
76-
- Install Bazelisk and no other dependencies, no need to run `sudo ./setup.sh`
77-
- Modify & build OpenROAD
78-
- Test built OpenROAD with a few ORFS flows
79-
80-
The Bazel support in OpenROAD and ORFS is work in progress and some Bazel experience is recommended before going spelunking in the Bazel builds.
81-
82-
Contributions welcome!
83-
84-
To build `designs/asap7/gcd:gcd_floorplan`:
85-
86-
cd flow
87-
(cd ../tools/OpenROAD && bazel build :openroad -c opt) && bazelisk build designs/asap7/gcd:gcd_floorplan
88-
89-
Or to run all flows currently available in Bazel
90-
91-
cd flow
92-
(cd ../tools/OpenROAD && bazel build :openroad -c opt) && bazelisk build ...
93-
94-
Note! ORFS uses the OpenROAD Bazel built binary in stop-gap way until OpenROAD has been switched to bzlmod, after which to build all flows becomes simpler as ORFS will build the requisite OpenROAD directly:
95-
96-
cd flow
97-
bazelisk build ...
98-
99-
ORFS uses [bazel-orfs](https://github.com/The-OpenROAD-Project/bazel-orfs) to implement the flow and gets some depedencies, like yosys, from the Docker image. Over time, all dependencies should be built with Bazel and the dependency on the ORFS Docker image will be phased out.
100-
101-
### Upgrading MODULE.bazel with the latest bazel-orfs and ORFS Docker image
102-
103-
Run:
104-
105-
bazelisk run @bazel-orfs//:bump
106-
107-
Then commit MODULE.bazel and MODULE.bazel.lock.

‎flow/README.md‎

Lines changed: 0 additions & 60 deletions
This file was deleted.

0 commit comments

Comments
 (0)