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
Our current submodule setup also requires the user to fork the OpenROAD repo for their fork of ORFS to be able to build.
We need to include this in the docs here and likely mention it in the main readme as well.
Expected Behavior
The command git clone --recursive <FORK_URL> should work on forks.
Environment
Does not apply.
To Reproduce
Fork ORFS.
Do not fork OR.
Clone ORFS and try to build.
Hi @maliberty, I see this issue is unassigned. I'm interested in GSoC 26 and would love to fix this. Can I work on it? I'll add forking instructions to the Git guide and README.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 21 days if no further activity occurs. Remove the Stale label or comment to keep it open.
I was looking into this issue and noticed that PR #4070 was recently merged to address the documentation generation workflow that affected the previous fixes. Does #2213 still require any additional changes, or has the issue been fully resolved by #4070?
Activity
Krupakar-Reddy-S commentedon Aug 3, 2024
i want to work on this
maliberty commentedon Aug 3, 2024
Thanks
YadavAkhileshh commentedon Feb 20, 2026
Hi @maliberty, I see this issue is unassigned. I'm interested in GSoC 26 and would love to fix this. Can I work on it? I'll add forking instructions to the Git guide and README.
shubhika123 commentedon Mar 29, 2026
Hello @maliberty , can I please be assigned this issue to work upon?
github-actions commentedon May 29, 2026
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 21 days if no further activity occurs. Remove the
Stalelabel or comment to keep it open.shubhika123 commentedon May 29, 2026
I was looking into this issue and noticed that PR #4070 was recently merged to address the documentation generation workflow that affected the previous fixes. Does #2213 still require any additional changes, or has the issue been fully resolved by #4070?
vvbandeira commentedon Jun 4, 2026
The issue has been fully resolved by #4070
Thanks for your contribution regardless