You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to optionally allow users to point to a local openroad openlane install in order to allow them to run it in environment where docker is not supported (i.e: https://colab.research.google.com/).
The text was updated successfully, but these errors were encountered:
It's a little bit less straightforward than that since we also do rely on a number of scripts inside the OpenLane container and we also rely on some OpenLane utilities such as magic for sign-off.
That said, assuming someone is willing to download an OpenLane repo and point to it + compile magic themselves, I'm not opposed to the idea.
Makes sense, so I should probably rename the issue to 'pointing to a local openlane' install :)
proppy
changed the title
dffram should allow pointing to a local openroad install
dffram should allow pointing to a local openlane install
Dec 13, 2021
https://github.com/Cloud-V/DFFRAM/blob/main/docs/Usage.md#using-dffram seems to suggest
docker
is only required to runplaceram
but in practice almost all the steps depends on theopenlane
functionrun_docker
invocation: https://github.com/Cloud-V/DFFRAM/blob/main/dffram.py#L77It would be nice to optionally allow users to point to a local
openroadopenlane install in order to allow them to run it in environment where docker is not supported (i.e: https://colab.research.google.com/).The text was updated successfully, but these errors were encountered: