Simplify font building.

Simplify font building.

Gets rid of intermediate .lisp files, and doesn't build tables except
for the braces.

Build emmentaler with python instead of pe.

[lemzwerg, 2012-02-25 07:22:00]

LGTM.

[Julien Rioux, 2012-02-25 12:44:23]

This adds a dependency on the python module fontforge. I think it should be
checked during ./configure but I'm not sure where to point you for accomplishing
that.

Regards,
Julien

http://codereview.appspot.com/5695061/diff/1/python/mf_table.py
File python/mf_table.py (right):

http://codereview.appspot.com/5695061/diff/1/python/mf_table.py#newcode3
python/mf_table.py:3: # mf-to-table.py -- convert spacing info in MF logs .
mf_table.py ?

http://codereview.appspot.com/5695061/diff/1/python/mf_table.py#newcode185
python/mf_table.py:185: 
git complains about new blank line at EOF here.

http://codereview.appspot.com/5695061/diff/1/scripts/build/gen-emmentaler.py
File scripts/build/gen-emmentaler.py (right):

http://codereview.appspot.com/5695061/diff/1/scripts/build/gen-emmentaler.py#...
scripts/build/gen-emmentaler.py:5: import fontforge
I got:
Traceback (most recent call last):
  File "/tmp/lilypond-autobuild/build/scripts/build/out/gen-emmentaler", line 5,
in <module>
    import fontforge
ImportError: No module named fontforge
make[1]: *** [out/emmentaler-11.svg] Error 1

http://codereview.appspot.com/5695061/diff/1/scripts/build/gen-emmentaler.py#...
scripts/build/gen-emmentaler.py:69: 
git complains about trailing whitespace here.

[hanwenn, 2012-02-25 12:57:09]

haven't looked in detail, but nice, and simpler than I thought :)

now, if you want a real challenge: you could redo mf2pt1 in Fontforge python
too! :)

[Julien Rioux, 2012-02-25 15:57:55]

This is good, I now get the error message right away when running configure. No
problem with the patch after installing the required package. Do lilydev and gub
already include the fontforge python package?

Regards,
Julien

http://codereview.appspot.com/5695061/diff/3003/configure.in
File configure.in (right):

http://codereview.appspot.com/5695061/diff/3003/configure.in#newcode175
configure.in:175: REQUIRED="$REQUIRED fontforge-python"
On ubuntu the package is named python-fontforge.

[Graham Percival, 2012-02-25 16:23:43]

On Sat, Feb 25, 2012 at 03:57:55PM +0000, julien.rioux@gmail.com wrote:
> This is good, I now get the error message right away when running
> configure. No problem with the patch after installing the required
> package. Do lilydev and gub already include the fontforge python
> package?

No, and adding this to GUB will be particularly challenging.  I'm
afraid that this will probably postpone the patch indefinitely.
:(

- Graham

[c_sorensen, 2012-02-25 16:50:33]

On 2/25/12 9:23 AM, "Graham Percival" <graham@percival-music.ca> wrote:

>On Sat, Feb 25, 2012 at 03:57:55PM +0000, julien.rioux@gmail.com wrote:
>> This is good, I now get the error message right away when running
>> configure. No problem with the patch after installing the required
>> package. Do lilydev and gub already include the fontforge python
>> package?
>
>No, and adding this to GUB will be particularly challenging.  I'm
>afraid that this will probably postpone the patch indefinitely.
>:(

Can't we add that package as a requirement for GUB (kind of like we have
done with libmpfr-dev)?  And we can add it to lilydev.


Thanks,

Carl

[Graham Percival, 2012-02-25 17:01:00]

On Sat, Feb 25, 2012 at 04:50:21PM +0000, Carl Sorensen wrote:
> On 2/25/12 9:23 AM, "Graham Percival" <graham@percival-music.ca> wrote:
> 
> >No, and adding this to GUB will be particularly challenging.  I'm
> >afraid that this will probably postpone the patch indefinitely.
> >:(
> 
> Can't we add that package as a requirement for GUB (kind of like we have
> done with libmpfr-dev)?  And we can add it to lilydev.

Hmm, I hadn't thought of that... but I don't like the idea.  Any
use of stuff from the host system adds variables to the process;
we already have too much randomness in terms of being able to
compile GUB on some computers but not others.

GUB really shouldn't use libmpfr-dev at all, nor fonts from the
host system, etc.  In fact, after it finishes make bootstrap, it
should remove any host system directories from the PATH, and/or
use a chroot to avoid picking up host-system stuff.  If we did
that -- after fixing bugs in the process, of course -- then we
could actually have a reliable GUB provided that it completed make
bootstrap.

- Graham

[joeneeman, 2012-02-25 22:06:46]

On Sat, Feb 25, 2012 at 8:23 AM, Graham Percival
<graham@percival-music.ca>wrote:

> On Sat, Feb 25, 2012 at 03:57:55PM +0000, julien.rioux@gmail.com wrote:
> > This is good, I now get the error message right away when running
> > configure. No problem with the patch after installing the required
> > package. Do lilydev and gub already include the fontforge python
> > package?
>
> No, and adding this to GUB will be particularly challenging.  I'm
> afraid that this will probably postpone the patch indefinitely.
> :(
>

Why would it be particularly challenging? In fact, since GUB builds
fontforge, the python bindings may already be included (I'm attempting to
check this now). It's just that debian-like distros feel the need to
separate each package into 5 pieces...

Cheers,
Joe

[Graham Percival, 2012-02-25 22:18:09]

On Sat, Feb 25, 2012 at 02:06:46PM -0800, Joe Neeman wrote:
>    On Sat, Feb 25, 2012 at 8:23 AM, Graham Percival
>    <[1]graham@percival-music.ca> wrote:
> 
>      No, and adding this to GUB will be particularly challenging.  I'm
>      afraid that this will probably postpone the patch indefinitely.
>      :(
> 
>    Why would it be particularly challenging? 

Whenever anybody tries to run GUB, there's a 1-20 hour setup time
while they run into various bugs.  A few people have tried it;
sometimes it "just works", other times it doesn't.  For reference,
Carl currently cannot build GUB, which is a shame since otherwise
he would be a candidate to work on the osx stuff (the only current
Critical bug which does not have a patch).

Once somebody has GUB running, and has a reasonable amount of
familiarity with python, compiling software, packaging, and old
python versions (GUB uses 2.4.5 IIRC), it would probably only be
about 30 minutes to get it working.  The problem is just getting
to that stage.

> In fact, since GUB builds
>    fontforge, the python bindings may already be included (I'm attempting
>    to check this now).

ah, that would be nice.  We would still need to update lilydev,
but that is not too hard.

- Graham

[hanwenn, 2012-02-27 12:15:04]

On Sat, Feb 25, 2012 at 8:06 PM, Joe Neeman <joeneeman@gmail.com> wrote:
> On Sat, Feb 25, 2012 at 8:23 AM, Graham Percival <graham@percival-music.ca>
> wrote:
>>
>> On Sat, Feb 25, 2012 at 03:57:55PM +0000, julien.rioux@gmail.com wrote:
>> > This is good, I now get the error message right away when running
>> > configure. No problem with the patch after installing the required
>> > package. Do lilydev and gub already include the fontforge python
>> > package?
>>
>> No, and adding this to GUB will be particularly challenging.  I'm
>> afraid that this will probably postpone the patch indefinitely.
>> :(
>
>
> Why would it be particularly challenging? In fact, since GUB builds
> fontforge, the python bindings may already be included (I'm attempting to
> check this now). It's just that debian-like distros feel the need to
> separate each package into 5 pieces...

It would be cleaner to change to build fontforge as a python extension
only, then we don't need to worry about graphic toolkits and such.

-- 
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen