Jim Meyering <[EMAIL PROTECTED]> writes: > Simon Josefsson <[EMAIL PROTECTED]> wrote: > ... >> I tried that now, since I kind of agree with the reasoning, although >> this breaks the maintainer-makefile module that I'm using in several >> projects. The module contains a 'GNUmakefile' that really need to be >> in the top-level directory to make sense. Any ideas how to resolve >> that? > > Hi Simon, > Your module could include a tiny configure.ac snippet to run this > > ln -s build-aux/GNUmakefile . > > That'll work as long as no GNUmakefile rule is supposed to run ./configure. > Then a Makefile snippet to remove it: > > MOSTLYCLEANFILES += GNUmakefile
Unfortunately, I have GNUmakefile rules that run both autoreconf and configure... I have a maint-mk.cfg which contains among other things: ,---- | ifeq ($(.DEFAULT_GOAL),abort-due-to-no-makefile) | .DEFAULT_GOAL := bootstrap | endif | | autoreconf: | test -f ./configure || autoreconf --install | | bootstrap: autoreconf | ./configure $(CFGFLAGS) `---- Then a simple 'make' in a fresh CVS checkout will do the right thing. /Simon
