Re: Best practise for aclocal paths in cross builds

[Nick Bowler]

Hi Ross,

Adding the automake list, because (mostly for historical reasons)
aclocal is actually part of automake, not autoconf.

On 2024-12-17 11:01, Ross Burton wrote:
> I’m trying to clean up our autoconf invocation and want to do things
> the “right” way.
> 
> We’re in a cross environment with split native/target sysroots which
> makes things interesting, as this means there are two places which I
> consider the “system ac directories”, the target and the native.

I don't really get it, why you would need different autoconf macro
directories for "the target and the native", but ok...

> Unfortunately you can’t pass a colon-separated list for —system-acdir
> so right now we’re effectively doing:

I believe the dirlist mechanism[1] for aclocal can be used to achieve
the result you are trying to achieve.

Either put a dirlist file in the specified directory which points to the
other one, or specify a totally different directory containing a dirlist
file that refers to both.

[1] https://www.gnu.org/software/automake/manual/automake.html#dirlist

Hope that helps,
  Nick.