googlefonts / googlefonts/gftools

Ninja builder cleanup

Open
#803 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
283
Forks
73
Avg merge
21h 25m
Merged PRs (30d)
8

Description

We're in the process of switching to the latest gftools using the Ninja-based builder. However, when I build a simple `.ufo` family, the build leaves behind an `instance_ttf` directory in the root of the directory and a `.designspace` file alongside the UFO sources.

My expectation is that temporary files are removed after the build and the source directory is not modified. Is this an intentional change?

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the build for a simple .ufo family with the Ninja-based builder and inspect the generated instance_ttf directory and .designspace file. Trace where these outputs are created or cleaned up, then verify that temporary files are removed and the source directory remains unchanged after the build.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.