- **Needs**:  -->  
- **Patch**: new --> needs_work
- **Type**:  -->  
- **Comment**:

fails make

~~~
...
Making mf/out/emmentaler-brace.otf 
Making mf/out/emmentaler-brace.svg 
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
 Based on sources from 11:21 UTC 24-Sep-2017-ML-D.
 Based on source from git with hash: 
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
 Based on sources from 11:21 UTC 24-Sep-2017-ML-D.
 Based on source from git with hash: 
Making mf/out/emmentaler-brace.woff 
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
 Based on sources from 11:21 UTC 24-Sep-2017-ML-D.
 Based on source from git with hash: 
Traceback (most recent call last):
  File "/home/james/lilypond-git/mf/gen-emmentaler-brace.fontforge.py", line 
46, in <module>
    os.remove(tmp)
OSError: [Errno 2] No such file or directory: 'tmp.feta-brace-scaled.pfb'
/home/james/lilypond-git/build/.././mf/GNUmakefile:137: recipe for target 
'out/emmentaler-brace.svg' failed
make[1]: *** [out/emmentaler-brace.svg] Error 1
make[1]: *** Waiting for unfinished jobs....
Cannot open /home/james/lilypond-git/build/mf/tmp.feta-brace-scaled.pfb
The requested file, tmp.feta-brace-scaled.pfb, does not exist
Traceback (most recent call last):
  File "/home/james/lilypond-git/mf/gen-emmentaler-brace.fontforge.py", line 
45, in <module>
    font.mergeFonts(tmp)
EnvironmentError: No font found in file "tmp.feta-brace-scaled.pfb"
/home/james/lilypond-git/build/.././mf/GNUmakefile:137: recipe for target 
'out/emmentaler-brace.otf' failed
make[1]: *** [out/emmentaler-brace.otf] Error 1
/home/james/lilypond-git/build/../stepmake/stepmake/generic-targets.make:6: 
recipe for target 'all' failed
make: *** [all] Error 2

~~~



---

** [issues:#5811] mf: use python scripting for generating Emmentaler fonts**

**Status:** Started
**Created:** Sat Feb 29, 2020 08:42 PM UTC by Han-Wen Nienhuys
**Last Updated:** Sun Mar 29, 2020 01:32 PM UTC
**Owner:** Han-Wen Nienhuys


This gets rid of the ugly generated FontForge scripts, and avoids some
intermediate files.

Remove sequencing on |pfb . This was introduced in e6a5019 (Jun 28
2012, "Clean fonts and docs makefiles"). The race conditions were
fixed in f6dc5e (May 15 2014, "Generate a .pe script for one design
size at a time.")

Remove XXX.fontname files. They appear to be unused.

https://codereview.appspot.com/553580043


---

Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to