[m-dev.] Extra "installation hierarchy" for private libraries?

[Fergus Henderson]

On 03-Dec-1998, Warwick Harvey <wharvey at cs.monash.edu.au> wrote:
> 
> One thing I do reasonably often is build my own private library modules, for 
> use in a number of different programs in different directories.
...
> It seems to me that the solution to this is to provide some support in the 
> Mercury scripts so that one can specify an alternative "installation 
> hierarchy" (or, more generally, a list thereof) which would be searched in 
> the same way as and in addition to the main installation hierarchy.  
> Ideally, one would just set a single flag in the Mmakefile, and everything 
> would work, regardless of grade or architecture (assuming one had installed 
> that particular combination :-).
> 
> Does this seem like a good idea / the right way to go about it?

That sounds OK to me.

Ideally there would also be some support for automatically installing
libraries into such an installation hierarchy, via rules in the
automatically generated `.dep' files.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "Binaries may die
WWW: <http://www.cs.mu.oz.au/~fjh>  |   but source code lives forever"
PGP: finger fjh at 128.250.37.3        |     -- leaked Microsoft memo.