PATCHES - Countdown to January 19
Back to the regular schedule! Here is the current countdown report. The next countdown will begin on 2024-01-18 A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: No patches in Push at this time. Countdown: !2232 Make Scheme command-line argument handling more robust - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2232 Review: !2234 Tidy up default tagline text - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2234 !2233 NR: Improve documentation of tweaking absolute dynamic marks - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2233 !2231 Make `-dshow-available-fonts` more robust - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2231 New: No patches in New at this time. Waiting: No patches in Waiting at this time. Cheers, Colin
Re: Installing guile-devel on MacOS M1
Hi Carl, > I also tried using HomeBrew (since there is no port for guile3, either). > > brew install guile got me a guile 3.0, which I was able to symlink to my > MacPorts tree, and when I run guile from the prompt, I get guile3. > > In the HomeBrew tree there is an include directory: > > /opt/homebrew/Cellar/guile/3.0.9/include/guile/3.0 > > that contains the following: > > libguile libguile.h readline.h > > and libguile has a whole bunch of headers in it. > > I tried symlinking this directory to my MacPorts tree under > > /opt/local/include/guile/3.0 > > (which parallels an installation under 2.2) I would strongly recommend against this. MacPorts is likely to get confused if you manually modify things under /opt/local/. > Anybody have any ideas how to solve this? Find the directory where Homebrew stores Guile's pkg-config configuration file, guile-3.0.pc, and use PKG_CONFIG_PATH=/that/directory/ ../configure Jean signature.asc Description: This is a digitally signed message part
Installing guile-devel on MacOS M1
I'm trying to get a native M1 MacOS build of Lilypond going. I've installed all of the packages listed at https://lilypond.org/doc/v2.25/Documentation/contributor/requirements-for-running-lilypond https://lilypond.org/doc/v2.25/Documentation/contributor/other and https://lilypond.org/doc/v2.25/Documentation/contributor/requirements-for-building-documentation I cloned the gitab repository and followed the instructions for an out-of-tree build I ran .autogen.sh, and then ran configure. During the configure run I got this output: WARNING: Please consider installing optional programs or files: dblatex ERROR: Please install required programs: guile-devel >= 2.2 I'm not worried about dblatex, but I need guile-devel >= 2.2 I've been installing all of the other packages with MacPorts, but there is no guile-devel port: carl@Carls-MBP-2 build % sudo port install guile-devel Password: Error: Port guile-devel not found I also tried using HomeBrew (since there is no port for guile3, either). brew install guile got me a guile 3.0, which I was able to symlink to my MacPorts tree, and when I run guile from the prompt, I get guile3. In the HomeBrew tree there is an include directory: /opt/homebrew/Cellar/guile/3.0.9/include/guile/3.0 that contains the following: libguile libguile.h readline.h and libguile has a whole bunch of headers in it. I tried symlinking this directory to my MacPorts tree under /opt/local/include/guile/3.0 (which parallels an installation under 2.2) I got this: carl@carls-mbp-2 include % ls -lsa /opt/local/include/guile/3.0 0 lrwxr-xr-x 1 root admin 50 Jan 17 11:54 /opt/local/include/guile/3.0 -> /opt/homebrew/Cellar/guile/3.0.9/include/guile/3.0 But after all this work, I still get the ../configure message saying I need guile-devel >= 2.2 (and I'd like it for 3.0). Anybody have any ideas how to solve this? THanks, Carl
Adjusting `\f`
I would like to change the definition of `\f` to something like this ```tex "f" = #(make-music 'AbsoluteDynamicEvent 'text "f" 'tweaks '(((DynamicLineSpanner . horizon-padding) . 0.1))) { \stemDown f'4\f f'4\p } ``` to handle issue #4159. However, if I do the above the `horizon-padding` property can no longer be overridden with `\tweak` or `\override`. How can I fix that? In other words, I would like to set the `horizon-padding` property for `\f` as if I provided a default value for the `DynamicLineSpanner` grob in `define-grobs.scm`. Werner