Compiling LilyPond - question and documentation
I've been experimenting with putting trace messages in Lily by editing the source, make and then using DDD to watch what's going on. My question: What's the simplest way to revert to the proper source, rather than the stuff I've edited, to ensure my source tree is clean? In doing this, I've been following the CG. In the instructions for LilyBuntu it's explicit about using an out-of-tree build (using a separate build directory). In much of the rest of the CG this seems to be ignored. -- Phil Holmes Bug Squad ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Compiling LilyPond - question and documentation
On 2 January 2011 12:45, Phil Holmes m...@philholmes.net wrote: I've been experimenting with putting trace messages in Lily by editing the source, make and then using DDD to watch what's going on. My question: What's the simplest way to revert to the proper source, rather than the stuff I've edited, to ensure my source tree is clean? In doing this, I've been following the CG. In the instructions for LilyBuntu it's explicit about using an out-of-tree build (using a separate build directory). In much of the rest of the CG this seems to be ignored. The simplest thing surely must be to make your changes in a separate git branch and just switch between that and master when needed. -- Sven Axelsson ++[+ -].+..+.+.-.+... +++.-.++..++.++.... ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Compiling LilyPond - question and documentation
On Sun, Jan 02, 2011 at 11:45:20AM -, Phil Holmes wrote: What's the simplest way to revert to the proper source, rather than the stuff I've edited, to ensure my source tree is clean? git reset --hard origin It's in the CG chapter on source code. In doing this, I've been following the CG. In the instructions for LilyBuntu it's explicit about using an out-of-tree build (using a separate build directory). In much of the rest of the CG this seems to be ignored. I've got a patch waiting for review that adds this to the compile chapter. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
