This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ok to use autogen to generate Makefile.in?... alternatives?


On Fri, Apr 05, 2002 at 08:24:02PM -0500, Nathanael Nerode wrote:
> OK, I'm getting some decent reasons not to use autogen.  I have also
> found it rather finicky, and the dependence on guile does trouble me
> (since guile is rather finicky).
> 
> I'm going to put the key code (from the utils case) which makes me want
> to use autogen here:
> 
> (from the template file)
> # Everything from here on down is generated by FOR loops in autogen.
> [+ FOR targets +]
> # Glue for [+target+].
> [+ FOR subdirs +]
> [+target+]-[+subdir+]: configure-[+subdir+]
> 	cd [+subdir+] && $(MAKE) [+target_flags+] [+target+]
> .PHONY: [+target+]-[+subdir+]
> [+ ENDFOR subdirs +][+ ENDFOR targets +]
> # Glue for configure.
> [+ FOR subdirs +]
> configure-[+subdir+]: [+subdir+]/Makefile
> [+subdir+]/Makefile: config.status
> 	test -d [+subdir+] || mkdir [+subdir+] ; \
> 	cd [+subdir+] && $(abs_srcdir)/[+subdir+]/configure $(subconfigure_args)
> .PHONY: configure-[+subdir+]
> [+ ENDFOR subdirs +]

Nathanael, I don't think there's anything in there that you can't do
with even the limited set of SH that we consider portable!  Have you
considered a Makefile.in.sh?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]