[EMAIL PROTECTED] writes:
> Hi,
>
> What should I do if I want to fix small (and possibly harmless)
> things (like the --enable-gui thing):
>
> 1. should I silently fix it (you'll figure it out from the cvs log)
> 2. should fix and post a message to the devel list
> 3. should ask if I should/coul
Pedro Kroger writes:
> [12:51:54] pythagoras kroger $ grep PANGO config.h
> #define HAVE_PANGO_CVS 1
> #define HAVE_PANGO_FC_FONT_MAP_ADD_DECODER_FIND_FUNC 1
>
> I'll recompile it, double checking if I missed something.
That's easy: look at the bottom of lily/lily-guile.cc. If you're
using a cor
Pedro Kroger writes:
> What should I do if I want to fix small (and possibly harmless)
> things (like the --enable-gui thing):
>
> 1. should I silently fix it (you'll figure it out from the cvs log)
Yes, please. Esp. for obvious mistakes like these.
> 2. should fix and post a message to the dev
Hi,
What should I do if I want to fix small (and possibly harmless)
things (like the --enable-gui thing):
1. should I silently fix it (you'll figure it out from the cvs log)
2. should fix and post a message to the devel list
3. should ask if I should/could fix it
Pedro
On Sun Jul 04, 2004 at 05:20:13PM +0200, Jan Nieuwenhuizen wrote:
> Could you verify that you have
> in your config.h?
[12:51:54] pythagoras kroger $ grep PANGO config.h
#define HAVE_PANGO_CVS 1
#define HAVE_PANGO_FC_FONT_MAP_ADD_DECODER_FIND_FUNC 1
I'll recompile it, double checking if I missed
On Sun Jul 04, 2004 at 05:05:14PM +0200, Han-Wen Nienhuys wrote:
> > Is the description for --enable-gui supposed to be this?:
> opps. fixes are welcome. :)
ok, fixed in CVS :-)
Pedro
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu
Pedro Kroger writes:
> Now it seems to be 'working' (i.e. found the modules), but I got
> /home/kroger/lilypond/install//share/lilypond/2.3.5/scm/framework-gnome.scm:129:5:
> While evaluating arguments to map in expression (map ly:pango-add-afm-decoder (quote
> #)):
Hmm, that's odd. --enable-
[EMAIL PROTECTED] writes:
> On Sun Jul 04, 2004 at 10:58:00AM +0200, Jan Nieuwenhuizen wrote:
> > Great. You should tell LilyPond (ie, GUILE and the dynamic loader)
> > about all this stuff you compiled (see output-gnome.scm)
>
> thanks for your email. I've added the output-gnome.scm as a file to
On Sun Jul 04, 2004 at 10:58:00AM +0200, Jan Nieuwenhuizen wrote:
> Great. You should tell LilyPond (ie, GUILE and the dynamic loader)
> about all this stuff you compiled (see output-gnome.scm)
thanks for your email. I've added the output-gnome.scm as a file to
be checked in the last announcement
A thought just occurred to me; we make a habit of listing bugreporters
in the THANKS file. Maybe you could also add names of the bug
reporters to the THANKS file, once their bug(s) have fixed and closed.
How about that?
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~h
Carl Sorensen writes:
> I'm ready to start work on developing a fret-diagrams context and
> engraver.
Great.
> So I rebuild lilypond, starting
> with
> ./autogen.sh --enable-debugging
>
> make all
This is OK.
> make install
This will strip the (debugging) symbols. You should be using
lily/
Pedro Kroger writes:
> sh guile-gnome.sh now runs fine and compile ok. But, what am I
> supposed to do next?
Great. You should tell LilyPond (ie, GUILE and the dynamic loader)
about all this stuff you compiled (see output-gnome.scm)
export
GUILE_LOAD_PATH=$HOME/usr/pkg/g-wrap/share/guile/s
12 matches
Mail list logo