Fixed bug #191
authorSam Lantinga <slouken@libsdl.org>
Thu, 13 Apr 2006 13:23:56 +0000
changeset 16225bbfc3e20e10
parent 1621 f12379c41042
child 1623 09375aed0208
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
     1.1 --- a/Makefile.in	Thu Apr 13 13:08:26 2006 +0000
     1.2 +++ b/Makefile.in	Thu Apr 13 13:23:56 2006 +0000
     1.3 @@ -46,7 +46,11 @@
     1.4  LT_REVISION = @LT_REVISION@
     1.5  LT_LDFLAGS  = -no-undefined -rpath $(libdir) -release $(LT_RELEASE) -version-info $(LT_CURRENT):$(LT_REVISION):$(LT_AGE)
     1.6  
     1.7 -all: Makefile $(objects) $(objects)/$(TARGET) $(objects)/$(SDLMAIN_TARGET)
     1.8 +all: $(srcdir)/configure Makefile $(objects) $(objects)/$(TARGET) $(objects)/$(SDLMAIN_TARGET)
     1.9 +
    1.10 +$(srcdir)/configure: $(srcdir)/configure.in
    1.11 +	@echo "Warning, configure.in is out of date"
    1.12 +	#(cd $(srcdir) && sh autogen.sh && sh configure)
    1.13  
    1.14  Makefile: $(srcdir)/Makefile.in
    1.15  	$(SHELL) config.status $@