On Sat, Nov 21, 2009 at 10:17 PM, David Kastrup <d...@gnu.org> wrote: >>> Modifying Lilypond, then recompiling and reinstalling. That's not the >>> most hack-friendly way. I am still finding my way around. >> >> You're only modifying .scm files, so there shouldn't be any >> recompiling/reinstalling involved. > > They are lilypond .scm files, so I need to edit them either in the > source tree (where they won't get consulted without reinstalling) or in > the installed tree (where they will get overwritten on reinstalling) or > in private directories (where I get into search order mess when > different versions are flying around).
The recommended method for doing this on linux is 1. edit files in the src tree 2. run lilypond as ./out/bin/lilypond from the toplevel of the build tree. then the symlink magic will make sure that system files come from the source tree. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
