Re: [PATCH] Remove data/Makefile.am.

[Joel E. Denny]

On Sun, 16 Nov 2008, Akim Demaille wrote:

> But what exactly does not work?  You can still do the same thing:
> 
> touch src/lalr.c && make CFLAGS="-O0 -g" src/lalr.o && make src/bison
> 
> make tests/testsuite && tests/testsuite -v 32
> 
> or simply make check TESTSUITEFLAGS='-v 32'
> 
> make doc/bison.info && info --file=doc/bison.info
> 
> The only difference is that you no longer run cd beforehand.  It's the same as
> using make -C, without -C.

I understand this.  My point is that the usual way to make individual 
files is broken and often in a deceptive way.  Also, the extra typing is 
mildly annoying.  I can retrain my habits for Bison, I can type a little 
extra, and new developers can learn, but I was wondering whether this 
discrepancy really serves a purpose.

> My principal motivation is to use distcc as much as I can.  With frequent
> rebasing and changes, switching from one branch to another, sequential builds
> were slowing down my process.   I have also learned to prefer single Makefiles
> in that the dependencies are much more correct.
> 
> All the potential for concurrency is not achieved yet, because I have yet to
> convert lib/.

Thanks for explaining.