2011/7/23 Trevor Daniels <t.dani...@treda.co.uk>: > > Jan Warchoł wrote Saturday, July 23, 2011 1:39 PM > >> 2011/7/21 Trevor Daniels <t.dani...@treda.co.uk>: >>> >>> If the compile and link succeed, you usually ctrl-C out of make >>> as soon as linking has finished so you can get on with testing. >>> So you need to see the relevant messages on the console >>> to determine this. >> >> I'm not sure if i understand your workflow, but I think a far better >> solution than watching console output is to use a script. I attach a >> scipt that i use for this, it saves me some time. > > Not really. If you have changed only one or two C++ routines > the compile and link part of make take only a few seconds. > There's no point in letting it go on to check all the doc files.
Ah, i didn't know that! This can be very useful. However, i tried doing make and i didn't knew when i could interrupt it :( > So really no time is wasted watching the console output. In > my case there are usually compile errors to fix most of the time, > so it takes even less time :) > > Actually Graham's suggestion to have a compile and link only > target in make was a good one. That would save having to > ctrl-C out. I'd like that too! thanks, Janek _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
