So I beleive the conclusion here is that "--always-make" is not
really compatible with autotools at the moment (or perhaps
self-referential makefiles in general?)
Sounds plausible to me.
I'll add a note in the automake manual about this. Can't think of
anything else feasible to do. --
On 2021-06-02 00:56, Karl Berry wrote:
Hi Johan,
make --dry-run --always-make
I'm somehow amazed these two options work together at all. They seem
mutually unintelligible. In any case, it's the first time I've heard of
this, so I don't have a best (or any) practice to suggest. Sorry.
Maybe
Hi Johan,
make --dry-run --always-make
I'm somehow amazed these two options work together at all. They seem
mutually unintelligible. In any case, it's the first time I've heard of
this, so I don't have a best (or any) practice to suggest. Sorry.
Maybe someone else here has some ideas.
I ima
I stumbled upon an issue when I recently switched to VSCode as editor.
I have several projects that have a full (medium-complex+) autotool
setup and they all work fine. However I discovered that VSCode in order
to initialize starts by running
make --dry-run --always-make
as first time initial
