Knowing make's current idea of where it is would still be nice even if it keeps changing.
I also would like to hook to the start and end of the execution of every recipe because there are many uses for this, one of which might be progress but triggering retries (when unreliable network shares are involved), logging what recipes failed with the return code so on are other use cases. You can do a lot of this if you write your makefiles specially but that's not much use for building things written by other people or other tools. Regards, Tim On 12 May 2012 06:38, Samkit Jain <samkit.fe...@gmail.com> wrote: > Yeah, I guess what I was thinking simple is more complex to code. > But considering this kind of request is coming to GNU make since a couple > years now(the first I saw was in 2007), there should be a way to handle it > in generic manner. > But obviously saying is easier than doing, so I will also start reading code > to understand the complexity myself. > > -- > - Samkit > > _______________________________________________ > Bug-make mailing list > Bug-make@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-make > -- You could help some brave and decent people to have access to uncensored news by making a donation at: http://www.thezimbabwean.co.uk/friends/ _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
