On 17 Dec 2024, at 18:23, Zack Weinberg wrote:
> The other thing that comes to mind is, if there were anyone working
> seriously on usage of autoconf *without* automake, that would make
> the move a lot more valuable. I know some people have tried that in
> the past but I don't think any of them
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 s
On Tue, Dec 17, 2024, at 12:24 PM, Ross Burton wrote:
> On 17 Dec 2024, at 17:17, Nick Bowler wrote:
>> Adding the automake list, because (mostly for historical reasons)
>> aclocal is actually part of automake, not autoconf.
>
> I’ve been using autotools for too many years and I _still_ forget wha
Hi,
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.
On 17 Dec 2024, at 17:17, Nick Bowler wrote:
> Adding the automake list, because (mostly for historical reasons)
> aclocal is actually part of automake, not autoconf.
I’ve been using autotools for too many years and I _still_ forget what tool is
where… Though considering what it does, it really
