Le jeudi 02 mars 2023 à 08:11 -0600, [email protected] a écrit : > Jean, > I’ve found your response, and I’ve updated my list subscription to my new > email. > > My reason for wanting this is that I need to generate several types of output > based on some other settings in my input file. For example, I need PDF output > for print, and PNG output in a couple different resolutions for projection on > a screen. This is for use in a church. > > One thought I had was to spawn another LilyPond so that I could specify > command line options based on the settings in my input file. I haven’t been > able to get this to work so far, for reasons I don’t understand. I tried this > using (system "lilypond -fpng file.ly"). I also tried Guile’s system*, but > got an unbind error. I’m using 2.22.2.
Did you mean “unbound error”? But what is the error precisely? Perhaps a better approach would be to define whatever settings you have outside of the LilyPond file, in a script invoking LilyPond, add compilation flags based on them, and also pass them to LilyPond using the `--evaluate` option ([https://lilypond.org/doc/v2.24/Documentation/usage/command_002dline-usage#basic-command-line-options-for-lilypond](https://lilypond.org/doc/v2.24/Documentation/usage/command_002dline-usage#basic-command-line-options-for-lilypond)).
signature.asc
Description: This is a digitally signed message part
