From 6976261e2f1814901936b15d9cec313825e47e50 Mon Sep 17 00:00:00 2001 From: Sam Lantinga Date: Thu, 13 Apr 2006 13:23:56 +0000 Subject: [PATCH] Fixed bug #191 [I opted to go for a warning, since I often tweak configure.in, but don't want to rebuild the entire project] One thing that was lost in the switch from automake to the new build system is that there is now no rule to build configure from configure.in. IMHO, if configure.in gets changed, then at the very least, the build system should print out a warning (better, again IMHO, an error) about this fact. Else, you easily forget about this when modifying configure.in. --- Makefile.in | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Makefile.in b/Makefile.in index 98bbc7615..6fa7022fd 100644 --- a/Makefile.in +++ b/Makefile.in @@ -46,7 +46,11 @@ LT_RELEASE = @LT_RELEASE@ LT_REVISION = @LT_REVISION@ LT_LDFLAGS = -no-undefined -rpath $(libdir) -release $(LT_RELEASE) -version-info $(LT_CURRENT):$(LT_REVISION):$(LT_AGE) -all: Makefile $(objects) $(objects)/$(TARGET) $(objects)/$(SDLMAIN_TARGET) +all: $(srcdir)/configure Makefile $(objects) $(objects)/$(TARGET) $(objects)/$(SDLMAIN_TARGET) + +$(srcdir)/configure: $(srcdir)/configure.in + @echo "Warning, configure.in is out of date" + #(cd $(srcdir) && sh autogen.sh && sh configure) Makefile: $(srcdir)/Makefile.in $(SHELL) config.status $@