https://open-source-silicon.dev
Join Slack
What is the correct usage of the variable CURRENT_STEP in the openlane Makefile? It seems like this ...
# openlane
m
What is the correct usage of the variable CURRENT_STEP in the openlane Makefile? It seems like this allows you to re-run starting from a step, but it always deletes the run directory for me...
h
The 
OPENLANE_BASIC_COMMAND
in 
openlane/Makefile
uses the 
-overwrite
flag that causes the run directory to be deleted before the next run. If you start the docker container manually, you can call call 
flow.tcl
step-by-step, e.g. using 
-from
or 
-to
, or continuing after an interruption. You can also place an 
interactive.tcl
script in your project's openlane directory.
m
Thanks. Hm, I don't want to run manually, so maybe I will just hack that flag out.
Seems like they should disable -overwrite if you pass CURRENT_STEP
@User How do you start the docker container manually? If I use openlane "make mount" it doesn't mount the caravel user project directory
(I could export that volume manually starting docker but this is getting too interactive)
h
I just made the new target in the Makefile where I replaced the docker command line with a simple bash
👍 1
m
Yeah, that's what they have in openlane. Odd that they don't have these already.
I'm trying to minimize my differences just for merging/maintenance reasons
👍 1
3 Views
Open in Slack
PreviousNext
Powered by

What is Linen?

Linen is a search-engine friendly community platform. We offer integrations with existing Slack/Discord communities and make those conversations Google-searchable.

Powered by