This simplifies the build infrastructure, because it obviates Makefile hacks to force a single lilypond-book processes during the build
https://codereview.appspot.com/555360043
fcntl
timing test
spaces
eager checksums
harden
Passes make. make check and a full make doc
lockfilename
This looks like it is still under discussion, so I am leaving this on review for now.
Sorry, mistake. Patch on countdown for March 3rd
rebase
Patch on countdown for March 5th
Patch counted down - please push.
commit 7ab9c8fa4faff7a513d0ecfbc7eecf7efd2b8ea8 Author: Han-Wen Nienhuys <hanwen@lilypond.org> AuthorDate: Sun Mar 1 17:47:53 2020 +0100 Commit: Han-Wen Nienhuys <hanwen@lilypond.org> CommitDate: Thu Mar 5 12:18:23 2020 +0100 Add a FS lock to lilypond-book This simplifies the build infrastructure, because it obviates Makefile hacks to force a single lilypond-book processes during the build This uses a fcntl-based lock, which is managed by the kernel. This means there is no chance of the locks going stale (except on NFS) Remove limitations on parallelism in build system.
fcntl
https://codereview.appspot.com/555360043
timing test
https://codereview.appspot.com/555360043
spaces
https://codereview.appspot.com/555360043
eager checksums
https://codereview.appspot.com/555360043
harden
https://codereview.appspot.com/555360043
Passes make. make check and a full make doc
lockfilename
https://codereview.appspot.com/555360043
Passes make. make check and a full make doc
This looks like it is still under discussion, so I am leaving this on review for now.
Sorry, mistake. Patch on countdown for March 3rd
rebase
https://codereview.appspot.com/555360043
Passes make. make check and a full make doc
Patch on countdown for March 5th
Patch counted down - please push.