Repository navigation
Split into mist (freetype frontend) and mist-core (dependency-free SDF core) - #2
Merged
Merged
Conversation
funbiscuit
force-pushed
the
extract-mist-core
branch
from
October 9, 2026 16:45
f957d55 to
1ff94a5
Compare
Owner
|
LGTM, thanks for the PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The SDF generation pipeline never needed freetype — only the glyph-outline front end does. As it stood, any project linking
mistpulled in freetype and libc, which made it impossible to bake SDFs inside a wasm32-freestanding engine. This split separates the two so the generator can run anywhere, while the freetype front end stays available for normal font usage.What
One package, two modules:
mist— the full library, public API unchanged.mist-core— new module: the geometry files and the SDF pipeline, with zero dependencies.The freetype frontend now works like any other consumer of the core: it decomposes glyph outlines through
ShapeSink(font-agnosticmoveTo/lineTo/quadTo/cubicTo/closeingestion) and callscore.generateSingle, which takes a caller-built shape plus em-unit advance/bearings instead of a codepoint.Notes
mistconsumers still download the freetype tarball (dependencies are package-wide, same as today), but the C code is only compiled when themistmodule is linked —mist-corealone never compiles C. Verified that the core builds forwasm32-freestandingwith no libc.