Self-hosted emergence-engineering/pcbjam (browser KiCad WASM) — CMMS embed fork. Upstream tracked as remote "upstream".
- TypeScript 49.1%
- C++ 36%
- Shell 4.2%
- C 2.9%
- JavaScript 2.6%
- Other 5.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Adds an end-to-end test that drives File→Open in pcbnew, injects the .kicad_pcb and .kicad_pro files into MEMFS at the dialog's default starting directory, drives the menu + filename text input + Enter accept path, and screenshots the loaded board. Parametrized for both kicad/demos/microwave (RF polygon footprints) and kicad/demos/pic_programmer (full multi-IC layout). Without the rtree fix bumped in via the kicad submodule, the load would abort on every PCB at rtree.h:1771 Classify; the test asserts no [RTREE-DIAG] line and no Aborted(. The post-load clipboard RuntimeError in __asyncjs__js_clipboardHasText is a separate, pre-existing wasm-port limitation that we explicitly do not regress on here. - tests/kicad/load-pcb.spec.ts: serial-mode parametrized spec - tests/kicad/load-pcb-probe.spec.ts: one-shot diagnostic probe for inspecting wxFileDialog state on the canvas - tests/kicad/utils/fs-inject.ts: FS.writeFile bridge from Node fs - tests/kicad/utils/board-ready.ts: poll-for-no-dialogs readiness - tests/baseline-screenshots/load-pcb-*.png: 6 baselines covering both demos at pcbnew-ready / dialog-open / loaded states - features/.../rtree-debug-findings.md: full diagnosis trail with an upstream-reportable summary the maintainer can lift verbatim - kicad submodule bumped to 07d8130d44 (shape_poly_set rtree fix) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
| docker | ||
| features | ||
| kicad@07d8130d44 | ||
| logs | ||
| research | ||
| scripts | ||
| tests | ||
| wasm | ||
| wxwidgets@6fb2eac257 | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| build.md | ||
| CLAUDE.md | ||
| DEBUG.md | ||
| learning.md | ||
| README.md | ||
KiCad WebAssembly Port
Run KiCad PCBnew in the browser using WebAssembly.
Quick Start
Full Build (KiCad + All Tests)
# 1. Initialize submodules
git submodule update --init --recursive
# 2. Build KiCad WASM (Docker, ~10 min incremental, ~1-2 hours full)
./docker/build.sh
# 3. Build wxWidgets for local testing
./scripts/build-wxuniversal-wasm.sh
# 4. Build wxWidgets test apps
./scripts/build-wasm-test.sh
# 5. Run all tests
cd tests && npm install
npm test # wxWidgets tests (256 tests)
npm run test:kicad # KiCad tests (2 tests)
wxWidgets Only (No Docker)
# Requires: Node.js 18+ (Emscripten SDK auto-installed on first build)
./scripts/build-wxuniversal-wasm.sh
./scripts/build-wasm-test.sh
cd tests && npm install && npm test
Project Structure
kicad-wasm/
├── kicad/ # KiCad source (git submodule)
├── wxwidgets/ # wxWidgets source (git submodule)
├── wasm/ # WASM compatibility layer
│ ├── bindings/ # Embind bindings for JavaScript
│ ├── cmake/ # CMake find modules
│ ├── kiplatform/ # Platform abstraction (app, UI, printing)
│ ├── libcontext/ # Coroutine/fiber implementation
│ ├── shims/ # Runtime JavaScript shims
│ └── stubs/ # Stub implementations (libgit2, curl)
├── scripts/ # Build scripts
│ ├── build-wxuniversal-wasm.sh # Build wxWidgets for WASM
│ ├── build-wasm-test.sh # Build wxWidgets test apps
│ ├── deps/ # Dependency build scripts
│ ├── kicad/ # KiCad build scripts
│ ├── common/ # Shared utilities
│ └── config/ # Build config wrappers
├── docker/ # Docker build environment
├── tests/ # Playwright E2E tests
│ ├── e2e/ # Test specs
│ └── apps/ # WASM test applications
├── tools/ # External tools (binaryen)
└── output/ # Build output (pcbnew.js, pcbnew.wasm)
Feature Branches
Each feature branch has a folder in features/<branch-name>/ containing:
- Documentation and research notes
root.patch- changes to main repokicad.patch- changes to KiCad forkwxwidgets.patch- changes to wxWidgets fork
Generate patches: ./scripts/create-feature-patches.sh [branch-name]
Two Build Workflows
1. KiCad Build (Docker)
Full KiCad PCBnew build using Docker:
# Build KiCad WASM
./docker/build.sh
# Copy output to test directory
./tests/scripts/setup-kicad-wasm.sh
# Run KiCad tests
cd tests && npm install && npm run test:kicad
Output: output/pcbnew.js, output/pcbnew.wasm
See build.md for detailed build documentation.
2. wxWidgets Test Apps (Local)
Build standalone wxWidgets test apps for feature testing:
# Build wxWidgets for WASM
./scripts/build-wxuniversal-wasm.sh
# Build test apps
./scripts/build-wasm-test.sh
# Run wxWidgets tests
cd tests && npm install && npm test
Output: tests/apps/standalone/
Prerequisites
For KiCad Build (Docker)
- Docker Desktop with 16GB+ RAM allocated
- 10+ GB disk space for build cache
For wxWidgets Build (Local)
- Node.js 18+ (for tests)
- Emscripten SDK (auto-installed on first build)
# Initialize submodules
git submodule update --init --recursive
# Install Emscripten SDK (auto-runs on first build, or run manually)
./scripts/setup-emsdk.sh
Testing
cd tests
npm install
# Run all tests
npm test
# Run specific tests
npm run test:kicad # KiCad tests only
npx playwright test menu # Menu tests only
See tests/README.md for test documentation.
Current Status
- wxWidgets WASM: Core widgets working (menus, dialogs, grids, trees, OpenGL)
- KiCad PCBnew: Builds and loads in browser, canvas rendering working
- In Progress: Testing wxWidgets features used by KiCad
Documentation
- Build System - Docker build details
- Docker README - Container setup
- Tests README - Test infrastructure
License
KiCad is GPL-3.0. This project follows the same license.