> While it's your project and you can do this if you want, making
> all objects depend on the makefile sounds like a really silly idea.
> Nobody wants to spend 30 minutes recompiling because they added one
> source file to a library, or because they added an additional test
> case.
>
> I sugge
On 2014-10-09 20:07 +0100, R. Diez wrote:
> > If "configure" is changing something, an easy and reliable option is
> > to ensure that it changes config.h (or some other configuration
> > header), which will naturally cause a rebuild of files that include
> > the header.
>
> This is not as straight
First of all, thanks for your e-mail.
> If "configure" is changing something, an easy and reliable option is
> to
> ensure that it changes config.h (or some other configuration header),
> which will naturally cause a rebuild of files that include the header.
This is not as straightforward as i
On 2014-10-09 14:53 +0100, R. Diez wrote:
[...]
> I noticed that, if I change the version number in the top-level
> configure.ac by amending the call to AC_INIT(), running "make" in the
> build directory automatically regenerates the 'configure' script and
> re-runs it. However, the C++ source file
