Re: Behaviour when using both "--dry-run" and "--always-make" together
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 imagine there must be some way to avoid the endless loop, but it's not something I'll ever have time/energy to debug. Any reasonable patch would be welcome, though. --best, karl.
Behaviour when using both "--dry-run" and "--always-make" together
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 initialization. This throws the makefile (or actuall the re-config) into an endless loop re-running "configure".I have also confirmed this behavior with the smallest possible autoconf/automake setup. I can also kind-of understand why this happens (and it seems make have an internal way to discover this exact situation with the special variable MAKE_RESTARTS that could possible be used to detect a cyclic behavior) Does anyone know if the combination of both these command line parameters are valid in an autotools context and if not, should it be considered a bug or just a non-supported use case? Is there a known best-practice workaround (before I go down the rabbit-hole of trying to find something myself)? /Johan
