Hello,
I am trying to update a build system using recursive Automake Makefiles so as to
remove Automake2 compatibilty warnings (and make it compatible with Automake 2
when that comes out).
Simply adding subdir-objects to AM_INIT_AUTOMAKE in configure.ac works for most
cases, but fails completely
some time, though it might wait several
weeks. If C++ precompiled headers use the same logic, it will add additional
motivation.
Best regards,
Yvan
De : k...@freefriends.org
Envoyé : jeudi 13 mai 2021 03:20
À : FOURNIER Yvan
Cc : automake@gnu.org
Ob
Hello,
Sorry for reacting a bit late to the January discussion about Autotool's future.
As a longtime user of the GNU Autotools for a large computational dynamics code
(code_saturne.org), here are a few hopefully constructive remarks about our
experience so far.
Sorry if my post is a bit
...@gnu.org
You can reach the person managing the list at
automake-ow...@gnu.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Automake digest..."
Today's Topics:
1. Re: Future plans for Autotools (FOURNIER Yvan)
2. Re: Future plans for
Hello,
I concurr.
In the case of the software I work on (code-saturne.org), we have in addition
chosen not to version generated files, so as to be more consistent with a
"maintainer mode" logic. Meaning that depending on the machine we install on,
we can get a different behavior, as we cannot
Hello,
Would keeping PYTHON_PREFIX but changing its default to the "classical" value
be a working solution for this ?
Best regards,
Yvan
Le 25 août 2021 07:08, j...@macports.org a écrit :
On 2021-8-25 10:14 , Karl Berry wrote:
> Ok, I guess we'll have to revert the Python change and make
