lilypond-devel
[Top][All Lists]
Advanced

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

Re: Building lilypond on osx


From: Jonas Hahnfeld
Subject: Re: Building lilypond on osx
Date: Fri, 20 May 2022 16:30:57 +0200
User-agent: Evolution 3.44.1

On Thu, 2022-05-19 at 21:50 +0200, Luca Fascione wrote:
> Thanks a lot Jonas, this is very helpful
> 
> On Thu, May 19, 2022 at 8:29 PM Jonas Hahnfeld <hahnjo@hahnjo.de>
> wrote:
> > The usually recommended way (and that's also what I use to build
> > the packages for macOS) is export PATH="$(brew --prefix
> > bison)/bin:$PATH" in the session before configuring. 
> 
> So I can rely on the build system capturing the resolved path to
> bison during configure, like it would for CXX/CXXFLAGS?
> Good to know, thanks

Hm, for some it does, for some it does not - bison seems to fall into
the latter category. So you probably also want to set PATH when
building or use the below method.

>  
> > You might also set specific envvariables (whose names you'd need to
> > look up in the configure script), but changing PATH usually works
> > fine.
> 
> I did look in the configure help, I couldn't find an env var to
> adjust how bison is resolved.

It's not mentioned in the help, but you can set all-caps variables of
the programs you want to specify, so for example BISON.

> I am passing in directories to resolve the fonts, for example (say --
> with-texgyre-dir=/usr/local/Cellar/texlive/58837_1/share/texmf-
> dist/fonts/opentype/public/tex-gyre/)
> There's quite a few to specify linkage behaviour that I did find
> though.
> 
> Can't say that I fully understand why we need both URW and Gyre
> fonts, I might ask Werner at some point.

URW++ and TeX Gyre are LilyPond's default text fonts. The build system
uses their paths to directly install them alongside LilyPond. In my
opinion, this is not a good idea but that's a story for another thread.

> Guile also seems awkward:
> 
> checking for guile-2.2 >= 2.2.0... no

This checks for the libguile library. If it's not found, you need to
set PKG_CONFIG_PATH to the path where your guile-2.2.pc is.

> <... snip ...>
> checking for guile... guile
> checking guile version... 3.0.8

This checks for the guile executable for use in one script. It's ok
that this is a different version, but I hope that I can rewrite that
one script in Python so that we use one language uniformly.

> Where is the testing/detection for Guile set up, roughly?

If you still want to check, it's in aclocal.m4 - the functions
STEPMAKE_GUILE and STEPMAKE_GUILE_DEVEL.


Cheers
Jonas

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

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