The-OpenROAD-Project / OpenROAD-flow-scripts
git clone https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts.git
🔥 on GitHub Trending today
OpenROAD's scripts implementing an RTL-to-GDS Flow. Documentation at https://openroad-flow-scripts.readthedocs.io/en/latest/
+1
stars, 24h · #531
+11
stars, 7 days · #1,572
+24
stars, 30 days · #9,945
773
★ total · +1% this week
546
forks · 51 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguageVerilog
License—
Created2020-07-28 (6y ago)
Last pushtoday
Watchers13
OwnerOrganization
Seen on GitHub Trending
- 2026-10-20 — #4 daily in verilog · +1 ★
- 2026-10-20 — #4 monthly in verilog · +24 ★
- 2026-10-20 — #2 weekly in verilog · +11 ★
GitHub topics
Links
- GitHub: github.com/The-OpenROAD-Project/OpenROAD-flow-scripts
- Homepage: https://theopenroadproject.org/
- Releases · Issues · Hacker News mentions
README excerpt
# OpenROAD Flow OpenROAD-flow-scripts (ORFS) is a fully autonomous, RTL-GDSII flow for rapid architecture and design space exploration, early prediction of QoR and detailed physical design implementation. However, ORFS also enables manual intervention for finer user control of individual flow stages through Tcl commands and Python APIs. [code] ## Tool Installation There are multiple ways to install and develop OpenROAD and ORFS. However, the best option depends on your use case, experience level, and personal preference. > **Recommendation for new users:** > If you are new to OpenROAD-flow-scripts, Docker can be a reliable way to get started since it avoids most dependency and environment issues. > > On supported platforms, using the pre-built binaries can be an even simpler option as it avoids building from source. > > Alternatively, the Bazel-based flow also avoids manual dependency installation (aside from installing Bazelisk itself), similar to how Docker requires installing Docker. ### Use Bazel, avoid installing anything at all and adapt the flow to your needs in your own repository bazel-orfs provides a seamless, reproducible way to manage dependencies and adapt the flow without requiring manual installations(no Docker images, sudo bash scripts, etc.) By leveraging Bazel's robust build system, all dependencies are automatically resolved, versioned, and built in a consistent environment. This eliminates setup complexity, ensures fast incremental builds, and allows for easy customization of the flow, making it an efficient choice for both beginners and advanced users. ### Docker Based Installation To ease dependency installation issues, ORFS uses docker images. Docker image includes ORFS binaries, applications as well as all required dependencies. All of the flow tools are encapsulated inside the container image. If `Docker` is not installed already, install latest docker tool based on OS from here. To manage docker as non-root user and verify that you can run `docker` commands without `sudo` must complete steps from here. #### Build ORFS with Docker Document for detailed steps on docker based installation found here. ### Pre-built Binaries You can download, set up and run ORFS easily with pre-built binaries, including OpenROAD, Yosys and Klayout. See instructions here. > **Thanks** to Precision Innovations for > providing and supporting OpenROAD based binaries. > **Note** Only the latest version of OpenROAD is guaranteed to work with > the latest version of ORFS. > **Disclaimer** The versions of OpenROAD, Yosys and Klayout provided by > other third-party vendors are not guaranteed to work with ORFS. ### Build from sources locally Document for detailed local build from sources and installation steps found here. ## Using the Flow - For details about the OpenROAD and the available features and individual flows commands, see the documentation here. - For details about automated flow setup, see ORFS docs here. - Flow tutorial to run th