> Things I can think of:
>
> - 'install' can be assumed to be OK.
> - 'mkdir' can be assumed to be OK.
> - I am always using GNU Make, so all 3 checks around make are dispensable.
> - I am always using GCC, so checking whether it accepts -g etc. is not
> necessary.
>
> Is there any article or bl
On 4/27/22 13:04, Alex Ameen wrote:
> You could setup a `config.site` file to share across projects. This is
> where I imagine you will get the most mileage.
>
> But it sounds like you can probably recycle `config.cache` for a single
> pipeline assuming you aren't changing the actual configure scr
You could setup a `config.site` file to share across projects. This is
where I imagine you will get the most mileage.
But it sounds like you can probably recycle `config.cache` for a single
pipeline assuming you aren't changing the actual configure script and
external inputs.
I saw your other mes
Hi all:
I have this cross-compiling Autoconf project:
https://github.com/rdiez/JtagDue/tree/master/Project
I am not using Autoconf for portability, but mainly for handling C/C++
dependencies, so that not everything is rebuilt when I change one source file.
This is just an example project, I h
