[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: if vs. ifdef in Makefile.am
From: |
Jan Engelhardt |
Subject: |
Re: if vs. ifdef in Makefile.am |
Date: |
Fri, 3 Mar 2023 15:37:37 +0100 (CET) |
User-agent: |
Alpine 2.25 (LSU 592 2021-09-18) |
On Friday 2023-03-03 13:14, ljh wrote:
>Thanks for the hint. I did not know this before.
>
>Found it here, autoconf manual 16.3:
>> cd to the directory where you want the object files and executables to
>> go and run the configure script. configure automatically checks for
>> the source code in the directory that configure is in and in ...
>> This is known as a VPATH build.
>
>$ bash ../src/autogen.sh
>autoreconf: 'configure.ac' or 'configure.in' is required
>$
>
>But `autoreconf -i` only runs in directory where configure.ac lives. It
>generates a lot temporary files in the source directory.
https://lists.gnu.org/archive/html/automake/2023-01/msg00005.html
- Re: if vs. ifdef in Makefile.am, (continued)
- Re: if vs. ifdef in Makefile.am, Arsen Arsenović, 2023/03/01
- Re: if vs. ifdef in Makefile.am, Bogdan, 2023/03/02
- Re: if vs. ifdef in Makefile.am, ljh, 2023/03/02
- Re: if vs. ifdef in Makefile.am, Jacob Bachmeyer, 2023/03/02
- Re: if vs. ifdef in Makefile.am, ljh, 2023/03/03
- Re: if vs. ifdef in Makefile.am, Jan Engelhardt, 2023/03/03
- Re: if vs. ifdef in Makefile.am, ljh, 2023/03/03
- Re: if vs. ifdef in Makefile.am, Jan Engelhardt, 2023/03/03
- Re: if vs. ifdef in Makefile.am, ljh, 2023/03/03
- Re: if vs. ifdef in Makefile.am,
Jan Engelhardt <=