pcbjam/wasm
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Viktor Vaczi 898e079ef2 Enable 3D viewer in KiCad WASM build
Build the 3D viewer code for WASM instead of stubbing it out.
This is simpler to maintain than complex header stubs.

Changes:
- Enable KICAD_BUILD_3D_VIEWER_WASM=ON in build script
- Remove -gsource-map to avoid OOM in wasm-emscripten-finalize
- Add OpenGL stubs for fixed-function pipeline (WebGL ES 2.0 only)
- Add GLU stub for gluErrorString
- Add NNG stub for IPC API (sockets don't work in WASM)
- Add PCBnew scripting stub
- Expand curl and libgit2 stubs

The 3D viewer code compiles but won't render at runtime since
OpenGL GAL is disabled and Cairo GAL is used instead.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-21 14:21:29 +01:00
..
cmake Add KiCad PCBnew WASM build support and documentation 2025-12-08 18:26:57 +01:00
kiplatform Add KiCad PCBnew WASM build support and documentation 2025-12-08 18:26:57 +01:00
libcontext Add KiCad WASM build infrastructure and dependency scripts 2025-12-04 13:15:04 +01:00
patches Add KiCad PCBnew WASM build support and documentation 2025-12-08 18:26:57 +01:00
stubs Enable 3D viewer in KiCad WASM build 2025-12-21 14:21:29 +01:00
CMakeLists.txt Add KiCad WASM build infrastructure and dependency scripts 2025-12-04 13:15:04 +01:00
README.md Add KiCad WASM build infrastructure and dependency scripts 2025-12-04 13:15:04 +01:00

WASM Compatibility Layer

This directory contains WASM-specific implementations that allow KiCad to run in a web browser without modifying KiCad's source code.

Principle

Instead of patching KiCad source files, we:

  1. Override include paths to use our headers first
  2. Provide alternative implementations for platform-specific code
  3. Link our libraries instead of system libraries

Directory Structure

wasm/
├── CMakeLists.txt          # Master CMake for compatibility layer
├── README.md               # This file
├── kiplatform/             # Platform abstraction implementations
│   ├── CMakeLists.txt
│   ├── app.cpp             # App lifecycle (paths, startup)
│   ├── drivers.cpp         # GPU detection (returns "WebGL")
│   ├── environment.cpp     # Environment variables (localStorage)
│   ├── io.cpp              # File I/O (WASM virtual filesystem)
│   ├── policy.cpp          # Security policy (always permissive)
│   ├── secrets.cpp         # Credential storage (localStorage)
│   ├── sysinfo.cpp         # System information
│   └── printing.cpp        # Print support (browser print())
├── libcontext/             # Coroutine/fiber implementation
│   ├── CMakeLists.txt
│   └── fcontext_wasm.cpp   # Emscripten Asyncify fibers
├── shims/                  # Header overrides
│   └── *.h                 # Headers that redirect to our impls
└── config/                 # Build configuration
    ├── kicad_wasm_config.h # Version and feature config
    └── setup.h             # Platform setup

How It Works

Include Path Override

When building KiCad for WASM, we add our directories first in the include path:

-I$PROJECT_ROOT/wasm/shims
-I$PROJECT_ROOT/wasm/kiplatform
-I$PROJECT_ROOT/stubs/include

This means when KiCad includes <kiplatform/app.h>, it finds our version first.

Library Override

We build libkiplatform_wasm.a and link it instead of the native kiplatform:

-L$BUILD_ROOT/wasm -lkiplatform_wasm

CMake Integration

The main KiCad build is configured to find our implementations:

-DCMAKE_MODULE_PATH="$PROJECT_ROOT/cmake"
-DKIPLATFORM_LIBRARY="$BUILD_ROOT/wasm/libkiplatform_wasm.a"

Adding New Implementations

  1. Create the implementation file in the appropriate directory
  2. Add it to the CMakeLists.txt
  3. Ensure the header interface matches KiCad's expected interface
  4. Test with a minimal build before full integration