I just posted the first version of completely rewritten scripts to
build static binaries for LilyPond:
https://gitlab.com/lilypond/lilypond/-/merge_requests/864

Some key design decisions are:
 * Build natively, avoid cross-compilation.
 * Use static builds of dependencies, no shared libraries.
 * Be specific to LilyPond, no generic package manager.
 * Use tarballs for sources, no download from git.
 * Keep it simple, stupid.

For more details and context, see the added README and
https://lists.gnu.org/archive/html/lilypond-devel/2020-03/msg00337.html
https://lists.gnu.org/archive/html/lilypond-devel/2021-05/msg00027.html

I think it would be best to have discussions about the higher-level
decisions on the mailing list (if needed), and code review in the form
of comments on the merge request itself.

Cheers
Jonas

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

  • [RFC] Add set of sc... Jonas Hahnfeld via Discussions on LilyPond development

Reply via email to