[mercury-users] Newbie question: what all these folders for?
pbone at csse.unimelb.edu.au
Fri Oct 3 15:06:25 AEST 2008
On Fri, Oct 03, 2008 at 03:03:40PM +1000, Julien Fischer wrote:
> On Fri, 3 Oct 2008, Peter Lemenkov wrote:
> >2008/9/30, Julien Fischer <juliensf at csse.unimelb.edu.au>:
> >> On Tue, 30 Sep 2008, Peter Lemenkov wrote:
> >>>* lib - also stronlgy required for Mercury to work. There are some
> >>>static libraries inside - we (at Fedora) have strict policy not to
> >>>package static libs until it would be absolutely necessary - I think
> >>>that's exactly the very case.
> >> In general both static and shared versions of the libraries are
> >> installed.
> >So does it means that I can safely remove all static (*.a) libraries?
> >As I said this is a strong requirement of Fedora Packaging Guide.
> You could do that although anyone who attempts to compile
> with --mercury-linkage=static is going to be in for a surprise ;-)
> (It is not uncommon to want to do that so that one can distribute
> executables that work on systems that do not have the Mercury libraries
> I am concerned that not including the static versions may cause users to
> the installation is broken.
> I imagine that the packaging guidelines were formulated for use with
> C or C++ libraries. What is appropriate for those languages may _not_
> necessarily be appropriate for Mercury. I would also note that Ocaml
> seems to have an exemption to the static linking parts of the Fedora
I recommened creating at least two packages,
Shared libraries and things needed to execute existing programs.
the Mercury compiler, mmake, static libraries and header files.
This should include everything desireable for writing programs in
This way you do not need to distribute the static libraries in the
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: Digital signature
More information about the users