[m-dev.] Installing and using private libraries

[David Jeffery]

On 21-Feb-2001, Ralph Becket <rbeck at microsoft.com> wrote:
> I've been trying to work out how one should use the mmake support
> for private libraries and I haven't had much luck.
>
> [...]
>
> However, if my makefile just looks like this
> (which is what the section "Supporting multiple grades and architectures"
> in the Users' Guide suggests to me should work)
> 
> EXTRA_LIB_DIRS = $(HOME)/local/mercury     # Is this necessary?
> EXTRA_LIBRARIES = foo

Hmmmm, this all works perfectly for me.

We use this mechanism to implement HALmake, which needs to let Mmake know how
to find the HAL runtime library ('libhal.a').

Basically, when installing our library (in this case installing it
into '/home/dgj/install/hal') we do:

mmake INSTALL_PREFIX=/home/dgj/install/hal LIBGRADES='...' install

Then, when halmake is invoked, we pass the following to mmake:

EXTRA_LIB_DIRS += /home/dgj/install/hal//lib/mercury
EXTRA_LIBRARIES += hal

Perhaps you have the path in 'EXTRA_LIB_DIRS' wrong? I am beginning to
suspect you are missing a '/lib/mercury/' from the end.

HTH.


dgj -- 
David Jeffery (dgj at cs.mu.oz.au) | If your thesis is utterly vacuous
PhD student,                    | Use first-order predicate calculus.
Dept. of Comp. Sci. & Soft. Eng.|     With sufficient formality
The University of Melbourne     |     The sheerist banality
Australia                       | Will be hailed by the critics: "Miraculous!"
                                |     -- Anon.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------