apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@attglobal.net>
Subject Re: apr-util buildconf copying rules.mk from ../apr
Date Tue, 04 Feb 2003 13:45:01 GMT
Sander Striker wrote:

> >From: Jeff Trawick [mailto:trawick@attglobal.net]
> >Sent: Tuesday, February 04, 2003 2:02 PM
> >It is helpful to be able to run buildconf prior to building APR. That
> >won't work anymore (ain't no ../apr/build/rules.mk prior to building 
> APR).
> >
> >This breaks Apache, which has buildconf that first runs apr buildconf
> >then apr-util buildconf.
> >
> >I thought the point of grabbing apr's rules.mk was to be able to build
> >apr-util from a pre-installed apr.
> Thing is that buildconf is for developers.  Release tarballs do not
> require buildconf to be run.  If you do not run buildconf, you can
> build apr-util with a pre-installed apr.
> What am I missing?

I'm a developer, and something that I want to do doesn't work anymore :)

Also, buildconf is for end users in some circumstances.  When part of 
the distributed toolchain (libtool, autoconf, whatever) is busted for 
somebody's platform, they have to install a working toolchain and run 
buildconf themselves to get started.

The copy of rules.mk isn't needed until after apr-util configure (i.e., 
the first chance for user to run "make"), so it can be copied at the end 
of configure when makefiles are being generated.  That way apr-util's 
buildconf can be run even if apr hasn't been configured yet.

Does anybody see a reason why copying rules.mk at the end of configure 
instead of in buildconf would be a problem?

View raw message