[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Which Linux distro for Lilypond
From: |
Knut Petersen |
Subject: |
Re: Which Linux distro for Lilypond |
Date: |
Thu, 12 Jan 2017 12:48:02 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 |
Hi Werner et al.!
*If* we bundle guile 1.8 with lilypond, I strongly prefer static
linking of the library (this is, adding `--disable-shared' to guile's
configure script, together with a proper argument to the
`--datarootdir' option to install the .scm files under a lilypond
directory). This avoids *any* problems with different guile library
versions, and the created lilypond binary can peacefully coexist with
guile 2.0 even in the `/usr' tree.
After a loser look at the sources and the build system I think it's better
(= much easier) to stay with shared libraries.
At runtime we do need both libguile and guile itself (it is used by
lilypond-invoke-editor), and all of our guile must be invisible to the
rest of the system.
That means:
+ there must be no entry in PATH leading to our private guile, guile-config etc.
+ there must be no entry leading to libguile etc in the system library search
path.
All that is possible without major changes to the sources... attached find a
bash
script as a proof of concept. The requirements described above are met.
It passes the "full make" test without problems:
address@hidden:~/sources>./mknewlily
Building GUILE 579b6041730357abcbb01e1f259e37c6e573cb7c first ...
First we add a library search path to libguile/dynl.c
exec ./autogen.sh in /home/knut/sources/guile ... succeeded after 14 seconds
exec ./configure --disable-error-on-warning
--prefix=/home/knut/sources/lilybuilt/share/lilypond in
/home/knut/sources/guile ... succeeded after 10 seconds
exec make -j 11 in /home/knut/sources/guile ... succeeded after 10 seconds
exec make -j 11 install in /home/knut/sources/guile ... succeeded after 1
seconds
Building LILYPOND 5bfd1e31928841704c5e5913290b948f6a480b09...
exec ./autogen.sh --noconfigure in /home/knut/sources/lily ... succeeded
after 1 seconds
exec ../configure --prefix=/home/knut/sources/lilybuilt in
/home/knut/sources/lily/build ... succeeded after 5 seconds
exec make -k -j 11 CPU_COUNT=11 all in /home/knut/sources/lily/build ...
succeeded after 92 seconds
exec make -j 11 CPU_COUNT=11 install in /home/knut/sources/lily/build ...
succeeded after 1 seconds
exec make -j 11 CPU_COUNT=11 doc in /home/knut/sources/lily/build ...
succeeded after 838 seconds
exec make -j 11 CPU_COUNT=11 install-doc in /home/knut/sources/lily/build ...
succeeded after 18 seconds
Total guile and lilypond build time: 990 seconds
cu,
Knut
mknewlily
Description: Text document
- Re: Which Linux distro for Lilypond, (continued)
- Re: Which Linux distro for Lilypond, H. S. Teoh, 2017/01/07
- Re: Which Linux distro for Lilypond, Trevor Daniels, 2017/01/07
- Re: Which Linux distro for Lilypond, H. S. Teoh, 2017/01/07
- Re: Which Linux distro for Lilypond, David Kastrup, 2017/01/07
- Re: Which Linux distro for Lilypond, H. S. Teoh, 2017/01/07
- Re: Which Linux distro for Lilypond, Knut Petersen, 2017/01/08
- Re: Which Linux distro for Lilypond, Paul, 2017/01/11
- Re: Which Linux distro for Lilypond, Werner LEMBERG, 2017/01/07
- Re: Which Linux distro for Lilypond, Knut Petersen, 2017/01/11
- Re: Which Linux distro for Lilypond, Werner LEMBERG, 2017/01/11
- Re: Which Linux distro for Lilypond,
Knut Petersen <=
- Re: Which Linux distro for Lilypond, Werner LEMBERG, 2017/01/13
- Re: Which Linux distro for Lilypond, Knut Petersen, 2017/01/14
- Re: Which Linux distro for Lilypond, David Kastrup, 2017/01/14
- Re: Which Linux distro for Lilypond, Werner LEMBERG, 2017/01/14