You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was running a build shell script and quite confused why my variable fonts were failing to build.
Turns out, I was specifying an --output-path for them to save to – without first creating a directory structure for those paths.
This seems redundant and unintuitive, especially because --output-dirwill create a required structure if it doesn’t exist.
Is this intentional? If so, can I ask the logic behind it?
Thanks!
Reproduction:
In this branch, running the ./fontmake-test.sh with FontMake 3.1.2 will reproduce this problem. Or, it seems that simply specifying a not-yet-created directory with the --output-path option will fail.
The text was updated successfully, but these errors were encountered:
I was running a build shell script and quite confused why my variable fonts were failing to build.
Turns out, I was specifying an
--output-path
for them to save to – without first creating a directory structure for those paths.This seems redundant and unintuitive, especially because
--output-dir
will create a required structure if it doesn’t exist.Is this intentional? If so, can I ask the logic behind it?
Thanks!
Reproduction:
In this branch, running the
./fontmake-test.sh
with FontMake3.1.2
will reproduce this problem. Or, it seems that simply specifying a not-yet-created directory with the--output-path
option will fail.The text was updated successfully, but these errors were encountered: