[m-dev.] issues with installing libraries
Zoltan Somogyi
zoltan.somogyi at runbox.com
Wed Sep 18 02:16:15 AEST 2024
On Sun, 15 Sep 2024 15:18:04 +0200 (CEST), "Zoltan Somogyi" <zoltan.somogyi at runbox.com> wrote:
> On Sun, 15 Sep 2024 09:34:57 +0200 (CEST), "Zoltan Somogyi" <zoltan.somogyi at runbox.com> wrote:
> > On Sun, 15 Sep 2024 14:20:13 +1000, Julien Fischer <jfischer at opturion.com> wrote:
> > > We should add something to compiler/notes documenting whatever the
> > > library installation
> > > structure is / becomes. (Although I am fairly certain you are
> > > intending to do that anyway.)
> >
> > Agreed on both counts.
>
> The attached diff documents both the existing setup,
> and the setup I think we should switch to. For post-commit review
> by *both* Peter and Julien, if you have the time.
In the absence of any reviews and/or objections by then,
in about 24 hours I intend to start implementing the PROPOSED scheme.
I intend to do this by keeping the existing install code, but adding to it
code to install things to the targets described by PROPOSED, which
all start with MercurySystem. Once that is done, I intend to add one or
more options that, when specified, switch the compiler's operation over
from searching for files in LEGACY places to searching for them in
PROPOSED places. We can keep dual LEGACY and PROPOSED installs
while we switch over to using PROPOSED exclusively in the Mercury
system, Prince, g12 etc, and use it for a while to establish reliability.
Once that is done, we can stop doing the LEGACY parts of installs,
and announce the changeover.
Zoltan.
More information about the developers
mailing list