On Sat, 21 Aug 2010, Ralf Wildenhues wrote:
So long ago already ...
Slow but sure ...
For some of the OSs the time is about the same if the directory is
already cleaned, while for others (e.g. OS-X) the time improves
considerably if the directory is already clean.
Here's a first patch I'm
So long ago already ...
* Bob Friesenhahn wrote on Wed, Oct 21, 2009 at 10:26:14PM CEST:
> On Wed, 21 Oct 2009, Ralf Wildenhues wrote:
> >>Is there a way to make this quite a lot faster?
> >
> >The LTLIBRARIES bits: yes, noted. The PROGRAMS bits should be
> >reasonably fast already, only forking
Bob Friesenhahn writes:
> Usually I don't care much about 'make clean' times but when I am
> chasing down compilation warnings I tend to do a lot of cleans.
When I'm chasing down compilation warnings I usually turn on
"-Werror" temporarily. Saves a lot of time.
--
Ben Pfaff
http://benpfaff.or
On Wed, 21 Oct 2009, Ralf Wildenhues wrote:
Is there a way to make this quite a lot faster?
The LTLIBRARIES bits: yes, noted. The PROGRAMS bits should be
reasonably fast already, only forking a constant number of times.
While clean is running, it is clear that the libraries bit is taking
m
Hi Bob,
* Bob Friesenhahn wrote on Wed, Oct 21, 2009 at 10:03:41PM CEST:
> clean-codersLTLIBRARIES:
> -test -z "$(coders_LTLIBRARIES)" || rm -f $(coders_LTLIBRARIES)
> @list='$(coders_LTLIBRARIES)'; for p in $$list; do \
> dir="`echo $$p | sed -e 's|/[^/]*$$||'`"; \
>
I find that 'make clean' is annoyingly slow. For my package 'make
clean' takes more than 1/10 of the optimized build time even though I
am using a very fast disk subsystem. For the clean target, Automake
produces many chunks which are of the form:
clean-codersLTLIBRARIES:
-test -z "$
