On 3 juil. 2012, at 19:46, Jean-Charles Malahieude wrote: > Le 03/07/2012 19:23, Janek Warchoł disait : >> Hi, >> >> until recently, 'make bin' was a very smart tool: it recompiled only >> necessary .cc files, not everything. That was lifesaving: instead of >> having to wait for 5 minutes, i got the results of my changes in 5 >> seconds. Unfortunately, this is no longer the case: no matter how >> trivial the change, make bin always goes through all .cc files. I've >> found that this behaviour was caused by commit >> 43fe858eb18418ae1d8867786ad873b7a4e2ae8a. I have no idea why this >> happens, but i guess this isn't an intentional change? I've checked >> that reverting this commit restores previous behaviour of make bin. >> > > Would not it be related with a clock problem? > Your box is running too fast for me! I wondered why your last commit is > always "right now", but when on > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=d00d0490996d794fb4b196e6e6c9664f554c370b > > I notice your last commit states: > > > authorJanek Warchoł <janek> > Fri, 6 Jul 2012 20:16:26 +0000 (22:16 +0200) > committerJanek Warchoł <janek> > Fri, 6 Jul 2012 20:16:26 +0000 (22:16 +0200) > commitd00d0490996d794fb4b196e6e6c9664f554c370b > > > HTH, > Jean-Charles > > > _______________________________________________ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel
If you just want to make the binaries, you can cc into the lily directory of your build directory and do a make all. Cheers, MS _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel