[m-rev.] for tryout and review: install .module_dep files to grade-specific directories

[Zoltan Somogyi]

On Sun, 1 Sep 2024 02:02:10 +1000, Julien Fischer <jfischer at opturion.com> wrote:
> >
> > Did you do what you did because there is something that prevents an mmc --make
> > based install from working for the other grades? If yes, what is the problem?
> 
> I built and installed Mercury in the way I usually do: mmake install
> It is mmake install itself that uses mmc --make to build and install
> the csharp and java grades
> (i.e. as part of the install_grades target); note that this happens
> regardless of whether
> --use-mmc-make is passed to mmake by the user.
> 
> In particular, at no point in the process did I specify --use-mmc-make to mmake.

I see that the code that does this is is the install_grades target in the top
Mmakefile in a workspace, NOT the lib%.install_grade target in scripts/Mmake.rules.
I will add it to the list of places which do (parts of) installs, and which need to be
updated if the install process changes.

> > Whether the sequence
> >
> > - a purely mmake based install of the library for the non-java, non-c# grades, and
> 
> As is hopefully clear from my comments above, "pure" mmake installs *do* use
> mmc --make when _installing the libraries_ in the csharp and java grades.
> Specifying --use-mmc-make is only useful when you want to build the
> entire Mercury system,
> using mmc --make.
> 
> > - an mmc --make based install (via mmake --use-mmc-make) of the library
> >   for the java and c# grades
> > should *even be expected to work* is one of the issues I posted.
> 
> Based on what the comments above the install_grades target say and also
> what has "worked" since the Java and C# grades were capable of being installed,
> I would say yes, it should be expected to work.

I was basing my original comment on the install code in Mmake.rules, not in the top
Mmakefile.

> > Please keep that install directory for a while longer. I intend to send an updated
> > diff in the next 24 hours that won't fix the problem, but will generate more debugging
> > output that I expect will give me at least some of the info I will need
> > to fix the problem.
> 
> Shall do.

The new diff, which replaces the old one, is attached. Please run
"mmc --make g12info" with an mmc containing this updated diff
against yesterday's install (though today's install would be identical),
and send me the output, which will still report failure, but this time should have
more debug info.

Thanks in advance,

Zoltan.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.mli4a
Type: application/octet-stream
Size: 22625 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20240901/8f145dd1/attachment-0001.obj>