On Nov 17, 2018, at 13:16, Mark Brethen wrote:
> The installation instructions for SPOOLES has this to say about multithreaded
> libraries:
>
> To build a multithreaded library, one must go to the MT/src directory. Now we
> have two choices — to build a separate spoolesMT.a library, or two merge the
> multithreaded code into the spooles.a library. We recommend the first, via
> typing make spoolesMT.a, though the second is perfectly fine by typing make
> makeLib. If Perl is not installed, type make -f makeGlobalLib for the latter
> behavior.
>
> Much the same applies to the MPI library. To build a MPI library, one must go
> to the MPI/src directory. Now we have two choices — to build a separate
> spoolesMPI.a library, or two merge the MPI code into the spooles.a library.
> We recommend the first, via typing make spoolesMPI.a, though the second is
> perfectly fine by typing make makeLib. If Perl is not installed, type make -f
> makeGlobalLib for the latter behavior.
>
> Is there a preference for macports build (i.e. merge them or build separate)?
I have no idea. I don't have any background about this software or how it's
typically used. Going with the developers' recommendation might be best, if
that's how other software that uses this library expects it to be packaged.
However, the whole static library (.a) thing is not especially desired in
MacPorts. We want dynamic libraries, for all the usual reasons.
