[m-dev.] a question about the proposed installed library directory structure

Julien Fischer jfischer at opturion.com
Wed Nov 6 10:31:57 AEDT 2024


On Wed, 6 Nov 2024 at 01:13, Zoltan Somogyi <zoltan.somogyi at runbox.com> wrote:
>
> The current PROPOSED directory structure for installed libraries
> (which is not yet used) installs .jar and .dll files to
>
> Prefix/MercurySystem/lib/Grade/main_module.jar and
> Prefix/MercurySystem/lib/Grade/main_module.dll respectively.
>
> However, the .a and .so files containing the compiled library
> in C grades are in
>
> Prefix/MercurySystem/lib/Grade/TargetArch
>
> which violates the principle that a directory in an installed library
> should contain either regular files OR directories, but not both.
>
> The attached committed diff makes minor improvements to
> english expression, but also adds an XXX about the above issue.
> The question is: should it be resolved by renaming
>
> Prefix/MercurySystem/lib/Grade/TargetArch to e.g.
> Prefix/MercurySystem/lib/Grade:TargetArch
>
> (maybe with a non-slash separator other than colon),

Colons are a reserved character in Windows paths, so don't use that!

> or should we install .jar and .dll files to
>
> Prefix/MercurySystem/jars/Grade/main_module.jar and
> Prefix/MercurySystem/dlls/Grade/main_module.dll respectively?
>
> I prefer the second option, because that fits in better with
> the rest of our naming scheme. What do you guys prefer?

My preference is for the second scheme.

Julien.


More information about the developers mailing list