libcascade

FAQ

Project lineage, maintenance, and how to contribute to libcascade.

What is the project lineage?

libcascade was originally created by Sebastian Alff (donalffons) as a port of OpenCASCADE Technology (OCCT) to WebAssembly via Emscripten. The current project is developed and released from taucad/opencascade.js.

libcascade does not modify the OCCT C++ source beyond a set of patches applied at build time. The pipeline downloads a tagged OCCT commit, compiles with Emscripten, auto-generates embind bindings from libclang, and ships the wasm + TypeScript surface as an npm package.

Who maintains it?

The maintainers and contributors at taucad/opencascade.js own current development, documentation, the GHCR image, and the libcascade npm package. Sebastian Alff is credited as the original author.

How can I contribute?

Contributions are welcome:

  1. Open issues or PRs at taucad/opencascade.js.
  2. Follow the existing code style and test conventions in the repo.
  3. Add focused tests for behavior changes and keep generated bindings generic at the C++ type-system level.

For larger architectural questions, start a discussion before opening a PR.

First Shape Tutorial

Build a filleted box from scratch, render it in three.js, and inspect the OCCT call sites.

Projects using libcascade

Public projects and reference repositories built on libcascade.

On this page

What is the project lineage?Who maintains it?How can I contribute?