From: Diego Biurrun <di...@biurrun.de>
During each make run, the build system checks that any specified dependencies
do actually exist, to prevent typos and other errors from fouling up correct
dependency settings. However, it also causes make to trip up when new
components have been added to the code, but not yet registered in the build
system by configure. A manual configure call is required in this case.
The "config" target is designed precisely to reinitialize the build without
having to manually call configure. Skip the dependency check when running
the "config" target to allow automatic reconfiguration in such cases.
Also skip the dependency check when doing clean, distclean, fate-rsync and
testclean.
---
tests/Makefile | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tests/Makefile b/tests/Makefile
index e32320d..e507c9e 100644
--- a/tests/Makefile
+++ b/tests/Makefile
@@ -24,7 +24,11 @@ tests/data/filtergraphs/%: TAG = COPY
tests/data/filtergraphs/%: $(SRC_PATH)/tests/filtergraphs/% |
tests/data/filtergraphs
$(M)cp $< $@
+# Do not check existence of config variables when reconfiguring to allow new
+# config variables getting registered in the build system.
+ifneq ($(filter-out clean config distclean fate-rsync testclean,
$(MAKECMDGOALS)), )
CHKCFG = $(if $($(1))$(!$(1)),$($(1)), $(error No such config: $(1)))
+endif
ALLYES = $(strip $(call XYES, $(1)))
XYES = $(if $(strip $(1)), \
--
1.7.9.4
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
