music stream exporter

[Kim Shrier]

I was reading Erik Sandberg’s master’s thesis,
http://lilypond.org/website/pdf/thesis-erik-sandberg.pdf
and I am curious if the music stream exporter still exists
and is operational.  A quick look through the sources
didn’t reveal anything to me but the existence of the
Dispatcher and  and Stream_event classes makes me
think that his modifications to Lilypond were integrated.

Any information about this would be appreciated.

Thanks,
Kim


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Error compiling Lilypond 2.19.81

[Karlin High]

On 4/11/2018 8:12 PM, Peter Engelbert wrote:
Perhaps it is wacky to install from the repository from an earlier 
version of Debian?  Is that unusual?


As long as it does what you want, that's the main thing.

I did once wreck a Linux install by adding repositories at random to 
Debian APT's sources.list file. That's what some website SAID to do... 
Suddenly I realized that my Debian system had become about 50% Ubuntu.


And it stopped doing what I wanted.

I'm fairly new to Linux though i 
have some background in programming, and I don't fully understand 
package management.


Been using Debian occasionally since Version 3 somewhere. I've learned 
some things, but won't claim to know much yet.


It looks like Debian does have ARM packages for LilyPond 2.19.81, 
although I don't know which ARM your Raspberry Pi needs. (Someday I want 
to get me one of those.)




No idea how that would turn out.

And if you haven't already seen it, the LilyPond Contributor's Guide has 
good step-by-step instructions for compiling from source.



--
Karlin High
Missouri, USA

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Error compiling Lilypond 2.19.81

[Peter Engelbert]

Hi Karlin,

thank you -- this is very good reading.  It's making my head spin, which
means I'm learning something :)  I was able to install guile 1.8 via the
repository for Debian Jessie. as far as I know I'm not using guile 2.x for
anything anyway, so i don't mind having 1.8 installed instead.

Perhaps it is wacky to install from the repository from an earlier version
of Debian?  Is that unusual?  I'm fairly new to Linux though i have some
background in programming, and I don't fully understand package management.

Thanks again,
Peter

On Wed, Apr 11, 2018 at 2:03 PM Karlin High  wrote:

> On 4/11/2018 3:48 PM, Peter Engelbert wrote:
> > In the meantime, I also noticed that for some reason Lilypond 2.18.2 is
> not
> > in the Debian Stretch (9) repository for ARM, but it IS in the Debian
> > Jessie (8) repository. So I was able to install 2.18.2 for the raspberry
> pi
> > by adding the Jessie repository. Is it’s absence in the Stretch
> repository
> > an oversight, or is there some reason for it?
>
> LilyPond depends on Guile 1.8; more recent versions are incompatible so
> far. Newer Debian versions have removed Guile 1.8. Here are a few
> threads from the lilypond-devel list that may be of interest.
>
> LilyPond in Debian
> 
>
> compiling lilypond in debian stretch with self-compiled guile-1.8
> 
> --
> Karlin High
> Missouri, USA
>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Error compiling Lilypond 2.19.81

[Daniel Johnson]

Gentoo ships a patch that has enabled me to build against Guile 2.2.3 
and run successfully:


http://mirrors.evowise.com/gentoo-portage/media-sound/lilypond/files/lilypond-2.19.80-remove-ly-protect.patch


On 4/11/18 5:03 PM, Karlin High wrote:

On 4/11/2018 3:48 PM, Peter Engelbert wrote:
In the meantime, I also noticed that for some reason Lilypond 2.18.2 
is not

in the Debian Stretch (9) repository for ARM, but it IS in the Debian
Jessie (8) repository. So I was able to install 2.18.2 for the 
raspberry pi
by adding the Jessie repository. Is it’s absence in the Stretch 
repository

an oversight, or is there some reason for it?


LilyPond depends on Guile 1.8; more recent versions are incompatible 
so far. Newer Debian versions have removed Guile 1.8. Here are a few 
threads from the lilypond-devel list that may be of interest.


LilyPond in Debian


compiling lilypond in debian stretch with self-compiled guile-1.8




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Error compiling Lilypond 2.19.81

[Karlin High]

On 4/11/2018 3:48 PM, Peter Engelbert wrote:

In the meantime, I also noticed that for some reason Lilypond 2.18.2 is not
in the Debian Stretch (9) repository for ARM, but it IS in the Debian
Jessie (8) repository. So I was able to install 2.18.2 for the raspberry pi
by adding the Jessie repository. Is it’s absence in the Stretch repository
an oversight, or is there some reason for it?


LilyPond depends on Guile 1.8; more recent versions are incompatible so 
far. Newer Debian versions have removed Guile 1.8. Here are a few 
threads from the lilypond-devel list that may be of interest.


LilyPond in Debian


compiling lilypond in debian stretch with self-compiled guile-1.8

--
Karlin High
Missouri, USA

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Error compiling Lilypond 2.19.81

[Peter Engelbert]

Thanks for the response, David. It prompted me to do my research regarding
make vs make install—I hadn’t previously realized there was a difference
between the two.

I’ll give it another shot, this time being sure to run make before make
install. I’ll report back after I’ve done that!

In the meantime, I also noticed that for some reason Lilypond 2.18.2 is not
in the Debian Stretch (9) repository for ARM, but it IS in the Debian
Jessie (8) repository. So I was able to install 2.18.2 for the raspberry pi
by adding the Jessie repository. Is it’s absence in the Stretch repository
an oversight, or is there some reason for it?

Once again, thanks for the response, and I’ll post back if the make doesn’t
go smoothly.

Be well,
Peter
On Wed, Apr 11, 2018 at 00:54 David Kastrup  wrote:

> Peter Engelbert  writes:
>
> > Hello illustrious Lilypond Developers,
> >
> > I am attempting to compile Lilypond from source.  I am most definitely in
> > over my head--but I did manage to install all of the dependencies, such
> > that running configure did not reveal any errors.
> >
> > I am compiling on Linux (specifically Raspbian, which is Debian Stretch
> on
> > ARM Architecture for Raspberry Pi).  The reason I'm compiling from source
> > is that there's no build available for ARM architecture from the lilypond
> > website.  When compiling (by running sudo make install), I receive the
> > following error.  I have no idea what it means, so I can't do anything to
> > fix it.  I am hoping that someone here can shed some light on what it
> means
> > so that I can get lilypond running on my Raspberry Pi!  Here is the error
> > message:
> >
> > rm -f ./out/parser.dep; DEPENDENCIES_OUTPUT="./out/parser.dep
> > ./out/parser.o" g++ -c -Woverloaded-virtual  -I/usr/include/python2.7
> > -I/usr/include/arm-linux-gnueabihf/python2.7  -fno-strict-aliasing -g
> > -fdebug-prefix-map=/build/python2.7-kKRR4y/python2.7-2.7.13=.
> > -fstack-protector-strong  -g -fwrapv  -DHAVE_CONFIG_H
> > -I/home/pi/repos/lilypond/lily/include -I./out
> > -I/home/pi/repos/lilypond/flower/include -I../flower/./out
> > -I../flower/include -I/home/pi/repos/lilypond/lily/out  -O2
> > -finline-functions -g -pipe  -I/usr/include/freetype2
> > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
> > -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
> > -I/usr/include/freetype2  -W -Wall -Wconversion -o out/parser.o
> > out/parser.cc
> > ./out/parser.cc: In function 'int yyparse(Lily_parser*,
> > scm_unused_struct**)':
> > ./out/parser.cc:2927:12: warning: conversion to 'yytype_int16 {aka short
> > int}' from 'int' may alter its value [-Wconversion]
> >*yyssp = yystate;
> > ^~~
> > make[1]: *** No rule to make target '../flower/./out/library.a', needed
> by
> > 'out/lilypond'.  Stop.
> > make[1]: Leaving directory '/home/pi/repos/lilypond/build/lily'
> > /home/pi/repos/lilypond/stepmake/stepmake/toplevel-targets.make:30:
> recipe
> > for target 'install' failed
> > make: *** [install] Error 2
> >
> > Thanks, and Godspeed.
>
> Do not run make install before running make.
>
> The extract of the log here is weird: it looks like Make is trying to
> link LilyPond before it is half-way finished compiling it or its
> prerequisites.
>
> So either your Make is seriously broken or your system date/time is
> running haywire and confusing it in this manner.
>
> --
> David Kastrup
>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Error compiling Lilypond 2.19.81

[David Kastrup]

Peter Engelbert  writes:

> Hello illustrious Lilypond Developers,
>
> I am attempting to compile Lilypond from source.  I am most definitely in
> over my head--but I did manage to install all of the dependencies, such
> that running configure did not reveal any errors.
>
> I am compiling on Linux (specifically Raspbian, which is Debian Stretch on
> ARM Architecture for Raspberry Pi).  The reason I'm compiling from source
> is that there's no build available for ARM architecture from the lilypond
> website.  When compiling (by running sudo make install), I receive the
> following error.  I have no idea what it means, so I can't do anything to
> fix it.  I am hoping that someone here can shed some light on what it means
> so that I can get lilypond running on my Raspberry Pi!  Here is the error
> message:
>
> rm -f ./out/parser.dep; DEPENDENCIES_OUTPUT="./out/parser.dep
> ./out/parser.o" g++ -c -Woverloaded-virtual  -I/usr/include/python2.7
> -I/usr/include/arm-linux-gnueabihf/python2.7  -fno-strict-aliasing -g
> -fdebug-prefix-map=/build/python2.7-kKRR4y/python2.7-2.7.13=.
> -fstack-protector-strong  -g -fwrapv  -DHAVE_CONFIG_H
> -I/home/pi/repos/lilypond/lily/include -I./out
> -I/home/pi/repos/lilypond/flower/include -I../flower/./out
> -I../flower/include -I/home/pi/repos/lilypond/lily/out  -O2
> -finline-functions -g -pipe  -I/usr/include/freetype2
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
> -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
> -I/usr/include/freetype2  -W -Wall -Wconversion -o out/parser.o
> out/parser.cc
> ./out/parser.cc: In function 'int yyparse(Lily_parser*,
> scm_unused_struct**)':
> ./out/parser.cc:2927:12: warning: conversion to 'yytype_int16 {aka short
> int}' from 'int' may alter its value [-Wconversion]
>*yyssp = yystate;
> ^~~
> make[1]: *** No rule to make target '../flower/./out/library.a', needed by
> 'out/lilypond'.  Stop.
> make[1]: Leaving directory '/home/pi/repos/lilypond/build/lily'
> /home/pi/repos/lilypond/stepmake/stepmake/toplevel-targets.make:30: recipe
> for target 'install' failed
> make: *** [install] Error 2
>
> Thanks, and Godspeed.

Do not run make install before running make.

The extract of the log here is weird: it looks like Make is trying to
link LilyPond before it is half-way finished compiling it or its
prerequisites.

So either your Make is seriously broken or your system date/time is
running haywire and confusing it in this manner.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel