8000 gftools builder uses `touch` command on Windows · Issue #1096 · googlefonts/gftools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

gftools builder uses touch command on Windows #1096

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
NightFurySL2001 opened this issue Apr 23, 2025 · 1 comment · Fixed by #1099
Closed

gftools builder uses touch command on Windows #1096

NightFurySL2001 opened this issue Apr 23, 2025 · 1 comment · Fixed by #1099

Comments

@NightFurySL2001
Copy link

Not sure how it happened, but on Windows 10 22H2 build 19045.5737, gftools.exe 0.9.79, running gftools builder config.yaml on the following yaml file raises an error that touch is not available on Windows.

config.yaml:

familyName: Font Name
buildVariable: true
buildStatic: false
buildTTF: false
buildOTF: true
autohintTTF: false
autohintOTF: false
sources:
- FontName.designspace

Log:

[1/3] buildVariable
cmd /c fontmake --output-path C:\Users\User\AppData\Local\Temp\tmp_g8i1q3p -o variable -m FontName.designspace --filter ... --filter FlattenComponentsFilter --filter DecomposeTransformedComponentsFilter
[2/3] fix
cmd /c gftools-fix-font -o ../fonts/variable\FontName[wght].ttf C:\Users\User\AppData\Local\Temp\tmp_g8i1q3p
[3/3] cmd /c gftools-gen-stat --inplace  -- "../fonts/variable\FontName[wght].ttf" && touch C:\Users\User\AppData\Local\Temp\tmp8twpgngt.buildStatstamp
FAILED: C:/Users/User/AppData/Local/Temp/tmp8twpgngt.buildStatstamp
cmd /c gftools-gen-stat --inplace  -- "../fonts/variable\FontName[wght].ttf" && touch C:\Users\User\AppData\Local\Temp\tmp8twpgngt.buildStatstamp
Saving font to ../fonts/variable\FontName[wght].ttf
'touch' is not recognized as an internal or external command,
operable program or batch file.
ninja: build stopped: subcommand failed
@simoncozens
Copy link
Contributor

This is indeed weird as our tests run on Windows! But maybe the GH runners have WSL installed or similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0