2011/7/21 Trevor Daniels <t.dani...@treda.co.uk>:
> In my case it's because I have difficulty in understanding precisely what
> the effect of this change will be on any work I do.
>
> But I have one comment.  By far the commonest use of make
> by developers is to compile the most recent change to C++
> source during the development cycle.  To speed this cycle
> up one usually watches the console to follow progress.
> If the compile fails you need to immediately see the error
> messages on the console.  It would be a nuisance if you had
> to fish these out from a file somewhere.
>
> 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.

HTH,
Janek

Attachment: makeandtest
Description: Binary data

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to