# HG changeset patch # User Sam Lantinga # Date 1144934636 0 # Node ID 5bbfc3e20e10e1c48c8118d25164a9a6e7e1c530 # Parent f12379c41042a42ea8108849f100a6f8459ea531 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. diff -r f12379c41042 -r 5bbfc3e20e10 Makefile.in --- a/Makefile.in Thu Apr 13 13:08:26 2006 +0000 +++ b/Makefile.in Thu Apr 13 13:23:56 2006 +0000 @@ -46,7 +46,11 @@ 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 $@