lilypond-devel
[Top][All Lists]
Advanced

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

Re: lilypond.org has wrong HTML files for 2.19.84


From: Werner LEMBERG
Subject: Re: lilypond.org has wrong HTML files for 2.19.84
Date: Wed, 04 Mar 2020 19:22:32 +0100 (CET)

>> OMG this is documented?  I wish I’d known all this weeks ago when I
>> was writing the Mac Makefile!

FYI, here is the first part of the relocation documentation.

  There’s actually a second mechanism for run-time configuration:
  LilyPond heavily relies on external programs and libraries, in
  particular the ‘FontConfig’ and ‘GUILE’ libraries to find system
  fonts and handle Scheme files, respectively, and the gs program to
  convert PS data to PDF files.  All of them must be configured also
  to locate its relevant data files.  To do that, the lilypond program
  parses all files in a directory called `relocate` (if it exists; see
  below where this directory is searched for) to manipulate
  environment variables, which in turn control those external
  libraries and programs.  The format of such relocation files is
  simple; each line has the syntax

    command key=value

  and empty lines get ignored.

  The `command` directive is one of the following.

    set         Uncondionally set environment variable key to
                value.  This overrides a previously set value.

    set?        Set environment variable key to value only if key
                isn’t defined yet.  In other words, it doesn’t
                override a previously set value.

    setdir      If value is a directory, unconditionally set
                environment variable key to value.  Otherwise, emit a
                warning.

    setfile     If value is a file, unconditionally set environent
                variable key to value.  Otherwise, emit a warning.

    prependdir  Prepend directory value to the list of directories in
                environment variable key. If key doesn’t exist it gets
                created.

  Environment variables (marked with a leading dollar sign) are
  allowed in value and get expanded before the directive is executed.

  Here are two examples of relocation file entries, taken from GUB
  (see Section “Grand Unified Builder (GUB)” in Contributor’s Guide).

    set? FONTCONFIG_FILE=$INSTALLER_PREFIX/etc/fonts/fonts.conf
    prependdir GUILE_LOAD_PATH=$INSTALLER_PREFIX/share/guile/1.8

  Multiple lines setting the same environment variable should be
  avoided in relocation files since the parsing order of files in the
  relocate directory is arbitrary.


    Werner

reply via email to

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