Closed bobh0303 closed 6 years ago
Example project: silnrsi/font-harmattan@3224f06e3d2341cc8cff558097bede26519b787b
Edit the fea(...)
function to add generated +
and the build fails.
psfmakefea is different from make_fea in that the former has to read the file directly while the latter inserts a path. So psfmakefea needs a path to the master from build directory and not the generated file's directory.
Huh? I didn't change the path to the master feax file. All I did was ask smith to place the built fea into a generated/
subfolder. Are you saying this is not allowed?
If the built fea file cannot go in a subfolder, such as generated/
, then the template that smith start
produces should not have
opentype=fea('source/' + 'opentype/' + APPNAME + '.fea',
it should have
opentype=fea(APPNAME + '.fea',
I would vote for the former, that is, allow the built fea to be placed in a subfolder.
Fixed in 4dfbe86ee2db8dd1a85559943b65b0d02d1350b3
When I changed
to
my build broke with this error:
using
smith build -v -j1
and comparing the commands used in each case, the failing case has an extra../
in front of the path to the .feax. (edited)I don't get similar failures for
so I'm wondering if this is a smith bug?