[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: unusable backtrace

From: Jean Abou Samra
Subject: Re: unusable backtrace
Date: Sun, 27 Mar 2022 21:46:06 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0

Le 27/03/2022 à 20:59, Werner LEMBERG a écrit :

    This is strange: What does '2.2-LE-8-3.A' mean?  Why do I get two
    paths concatenated?  Additionally, the `.go` files are put into
Because of Lilypond's functions exported from C++, which are added
only when running Lilypond but are needed for byte-compilation, we
cannot use the normal method to get .go files, 'guild compile'.  We
thus hijack the 'auto-compilation' happening when Guile runs a
Scheme file that doesn't have a compiled version in cache.  The
cache in question is usually under ~/.cache/guile, but we change the
directory.  Still, the principle remains: paths on your computer are
mirrored in the cache.  Yes, this is a PITA: much better would have
been to put the .go files next to the .scm files, so an install can
be moved around.  Guile's way of doing things basically would work
if byte-compilation were fast and silent, neither of which is the
case.  So, after this is done, we move the bytecode into scm/out/,
and at runtime we load it from there. See scm/GNUmakefile.
Thanks for the explanations.  It seems to me we should emit Guile's
messages only if `VERBOSE=1`.  Additionally, we should output the
usual one-liner for `VERBOSE=0`.

You mean the ';;; compiling ...' messages? If there is a way
to control them, I am not aware of it. See also


reply via email to

[Prev in Thread] Current Thread [Next in Thread]