[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_CONFIG_AUX_DIR + AC_CONFIG_SUBDIRS (Was: Re: (no subject))
From: |
Ralf Corsepius |
Subject: |
Re: AC_CONFIG_AUX_DIR + AC_CONFIG_SUBDIRS (Was: Re: (no subject)) |
Date: |
04 Aug 2003 09:20:06 +0200 |
On Sun, 2003-08-03 at 23:20, Alexandre Duret-Lutz wrote:
> >>> "Ralf" == Ralf Corsepius <address@hidden> writes:
>
> Ralf> AC_CONFIG_AUX_DIR however can be shared between several
> Ralf> configure.acs (AC_CONFIG_SUBDIRS).
>
> Do you do this?
Well, I was referring to such kind of situations:
* A top level configure-script accessing several config-subdirs:
# cat configure.ac
..
AC_CONFIG_AUX_DIR(.)
..
AC_CONFIG_SUBDIRS(sub1 sub2 sub3)
..
* With each subN/configure.ac containing:
# cat sub1/configure.ac
...
AC_CONFIG_AUX_DIR(..)
..
or not explicitly setting AC_CONFIG_AUX_DIR
=> All subN/configure.acs and configure.ac will share <toplevel> as
config-auxdir.
This had worked for ages (It is the default behavior).
And yes, I am using it.
> I wouldn't expect `make dist' to work in subdir
> projects configured this way.
Yes, a "subdir" 'make dist' in most cases doesn't work, but a "toplevel"
'make dist' normally does.
> So far, my impression is that the only way to allow subdir `make
> dist' is to duplicate the aux files in all subprojects. (This
> also means adding AC_CONFIG_AUX_DIR(.) to projects not already
> using AC_CONFIG_AUX_DIR.)
Agreed.
> This of course assumes that one wants to allow `make dist' in
> sub projects, which I guess is not always true.
Exactly.
Ralf