#1083 [System Wide OpenLane] Avoid hardcoded paths in sample designs. Pull request opened by cbalint13 Avoid hardcoded path in the setups of the sample designs. Design configs should be consistent regarding issues with path hard-coding. * * * A sample effort of system-wide OpenLane distributable is available here. The structure of distributables:

$ rpm -ql openlane
/usr/bin/openlane-flow.tcl
/usr/share/openlane/configuration/{..}
/usr/share/openlane/scripts/{..}
/usr/share/tcl8.6/openlane-tcl_commands/*
/usr/share/tcl8.6/openlane-utils/*
/usr/share/doc/openlane/{..}

$ rpm -ql openlane-designs
/usr/share/openlane/designs/{..,}

$ rpm -ql efabless-open-pdks-sky130_fd_sc_hd
/usr/share/pdk/sky130{A,B}/{...}

1. The

/usr/bin/openlane-flow.tcl

is system-wide executable (the

openlane-

suffix avoids confusion). 2. Modules in

/usr/share/tcl8.6/

are by default in system reach on

any distro

, they are picked up anytime. 3. The

/usr/share/openlane/

is also system wide and picked up by

/usr/bin/openlane-flow.tcl

itself. 4. The PDK (separate packages) is also in standard stystem path of

/usr/share/pdk/sky130{A,B}

Details of packaging: • openlane.spec • efabless-open-pdks.spec builded out from open-pdk-skywater.spec • The numerous rest of required tooling are all holded in this repo as individual packages. Thank you, ~Cristian @donn @vvbandeira @proppy Cc @maliberty The-OpenROAD-Project/OpenLane GitHub Actions: Test Design spm ✅ 17 other checks have passed 17/18 successful checks