Skip to content

Latest commit

 

History

History
38 lines (28 loc) · 953 Bytes

README.md

File metadata and controls

38 lines (28 loc) · 953 Bytes

The OpenLane Docker Image

Structure

There are two "families" of images: one is for building tools, and the other is the final OpenLane image.

The final OpenLane image contains all the tools necessary, meanwhile, the build family has a base image that contains all build dependencies and then a number of subimages tasked with building each tool.

openlane-build-base
L cugr
L cvc
L openroad_app
L [...]

openlane

Building the OpenLane Image

Tool binaries are currently stored under tar/. This was not a good idea, but it's what has happened.

If you want to just build the OpenLane image with the binaries checked into the Repo history, you can invoke:

make merge
# or alternatively: `make openlane`

Updating a Tool Binary

You can update a tool binary as follows:

make build-<tool_name>

The following are the available tools:

cugr drcu yosys magic openroad_app padring netgen vlogtoverilog cvc