[m-rev.] for review: keep the invocation automatically up-to-date

[Peter Wang]

On Sun, 20 Jul 2025 22:44:44 +1000 Julien Fischer <jfischer at opturion.com> wrote:
> On Sat, 19 Jul 2025 at 07:43, Zoltan Somogyi <zoltan.somogyi at runbox.com> wrote:
> >
> > The main issue I am seeking feedback on is that after this diff,
> > making the user guide requires compiler/mercury_compile to be
> > up to date. The other rules of doc/Mmakefile already depend
> > on the contents of the compiler directory, but they do so only for
> > .m files, which do not need to be built.
> 
> There is one case where this is a problem, namely building the source
> distribution.
> In that case mercury_compile will not exist when we build the doc directory.
> 

We also cannot assume that ../compiler/mercury_compile is executable
when cross-compiling.

I assume the solution is also to invoke the bootstrap compiler
when CROSS_COMPILING=yes.

However, I'm partial to committing the generated ug_invocation.texi file,
and simply not trying to regenerate it when we don't have an executable
stage1 compiler.

Peter