diff options
| author | Cory Fields <cory-nospam-@coryfields.com> | 2017-04-18 19:14:22 -0400 |
|---|---|---|
| committer | Jonas Schnelli <dev@jonasschnelli.ch> | 2017-05-31 10:54:19 +0200 |
| commit | ae479bc45bfdfb33e7f1293391db5b9f81b3ce17 (patch) | |
| tree | e3cb10cbcfff0454e64272afdc1a43faafed6181 | |
| parent | 3d395d6815e36850db0af4153756352bcc9c356a (diff) | |
| download | bitcoin-ae479bc45bfdfb33e7f1293391db5b9f81b3ce17.tar.xz | |
build: fix bitcoin-config.h regeneration after touching build files
This was a long-standing and annoying problem.
If autogen.sh was not manually run after touching configure.ac,
bitcoin-config.h would not be properly regenerated. This causes very subtle
problems when configure appears to enable a new value, but it does not end up
reflected in the build.
| -rw-r--r-- | src/Makefile.am | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/src/Makefile.am b/src/Makefile.am index e8d22313dc..76dbbced6c 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -457,6 +457,14 @@ DISTCLEANFILES = obj/build.h EXTRA_DIST = $(CTAES_DIST) + +config/bitcoin-config.h: config/stamp-h1 + @$(MAKE) -C $(top_builddir) $(subdir)/$(@) +config/stamp-h1: $(top_srcdir)/$(subdir)/config/bitcoin-config.h.in $(top_builddir)/config.status + $(AM_V_at)$(MAKE) -C $(top_builddir) $(subdir)/$(@) +$(top_srcdir)/$(subdir)/config/bitcoin-config.h.in: $(am__configure_deps) + $(AM_V_at)$(MAKE) -C $(top_srcdir) $(subdir)/config/bitcoin-config.h.in + clean-local: -$(MAKE) -C secp256k1 clean -$(MAKE) -C univalue clean |