On Mon, Mar 26, 2012 at 6:05 PM, Gert Doering <g...@greenie.muc.de> wrote: > Hi, > > one of the things the new build system brought is us is *this*: > > if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../src/compat > -I/usr/include -I/usr/include -g -O2 -MT ssl_verify_polarssl.o -MD -MP > -MF ".deps/ssl_verify_polarssl.Tpo" -c -o ssl_verify_polarssl.o > ssl_verify_polarssl.c; then mv -f ".deps/ssl_verify_polarssl.Tpo" > ".deps/ssl_verify_polarssl.Po"; else rm -f ".deps/ssl_verify_polarssl.Tpo"; > exit 1; fi > if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../src/compat > -I/usr/include -I/usr/include -g -O2 -MT status.o -MD -MP -MF > ".deps/status.Tpo" -c -o status.o status.c; then mv -f ".deps/status.Tpo" > ".deps/status.Po"; else rm -f ".deps/status.Tpo"; exit 1; fi > if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../src/compat > -I/usr/include -I/usr/include -g -O2 -MT tun.o -MD -MP -MF > ".deps/tun.Tpo" -c -o tun.o tun.c; then mv -f ".deps/tun.Tpo" > ".deps/tun.Po"; else rm -f ".deps/tun.Tpo"; exit 1; fi > > ... instead of straightforward "gcc" invocations. > > ... and I wonder what the benefit is? I find it much harder to see what > "make" is doing here (my eyes hurt when I look at this!), and unless there > is a clear benefit, I don't like adding convolutions...
The benefit is to divide the code into libraries and core which is easier to maintain and reuse. Anyway, new automake does support silent rules, try the following[1] patch and see if it makes you happier. Again, this demonstrate how current merge procedure is inappropriate, as instead of single build system rewrite merge we have aftershocks. Branch should be tested and reviewed, and tested and reviewed until no known issues found, and all happy of its quality. Alon. [1] https://github.com/alonbl/openvpn/commit/c35c118767d4867303e43c4472720dd94187aae5