Programm architecture simplified so that the EDA can now run individually without generation of .gds file

This commit is contained in:
2026-06-01 09:19:44 +08:00
parent 78f38d3be7
commit 7cf618fe02
160 changed files with 1640 additions and 11497 deletions
+14
View File
@@ -6,6 +6,13 @@ Organization : OptiHK Limited
-->
# mxPIC EDA Intranet Deployment
## Build-Time Router Stack
The Flask server can launch for login, dashboard, canvas editing, YAML
generation, and PDK browsing without importing `mxpic_router` or `mxpic_forge`.
Build actions require the matched `mxpic_router` and `mxpic_forge` checkouts;
SVG preview generation also requires `gdstk`.
## Start on the office LAN
1. On the host computer, open PowerShell in this repository.
@@ -64,6 +71,13 @@ MXPIC_PORT=3000
MXPIC_DEBUG=0
MXPIC_SECRET_KEY=<long random string>
MXPIC_COOKIE_SECURE=0
MXPIC_PDK_PUBLIC_ROOT=<path-to-public-foundries>
MXPIC_PDK_ATLAS_ROOT=<path-to-atlas-foundries>
```
Set `MXPIC_COOKIE_SECURE=1` only when serving through HTTPS.
PDK component metadata, GDS assets, and `technology.yml` manifests are all read
from these role-scoped roots. If the variables are not set, the backend defaults
to `../opt_pdk_public/foundries` for normal users/developers and
`../opt_pdk_atlas/foundries` for managers.