[Mono-devel-list] Hardcode $(prefix)/lib for assemblies rather than use $(libdir)

Michal Moskal michal.moskal at gmail.com
Wed Mar 23 11:37:45 EST 2005

On Tue, 22 Mar 2005 21:09:04 -0500, Ben Maurer <bmaurer at ximian.com> wrote:
> Hey guys,
> We have been having problems packaging on amd64. Basically, the issue is
> that we need to install .so files to /usr/lib64, but (apparently, and I
> don't know why here) we want to install assemblies to /usr/lib. I have
> attached a patch that does this.

I guess it is not the way to go. The dlls are installed to lib64 after
my patch. If ./configure is passed --libdir=/usr/lib64, I don't think mono's
makefile should be wiser than the user and install elsewhere.

> Installing to /usr/lib for .dll files seems weird for a few reasons:
>       * The decision to install to lib (vs share) implies that we want
>         the freedom of arch dependent assemblies. Wouldn't this imply
>         that we want to install to lib64?

I guess the best way to go here would be to install to /usr/share. If
the GAC is going to support AOT-ed assemblies, then it should be in
two locations -- /usr/share (dll files) and /usr/lib (or /usr/lib64,
.so files).

Or maybe there is something architecture specific in the IL assemblies
I don't know about?

>       * We would have to install the .pc files for, eg, gtk# into lib64,
>         as the lib version of the pkgconfig dir isn't searched. This
>         would be a bit funky

Well, I would call this ugly ;)

: Michal Moskal :: http://nemerle.org/~malekith/ :: GCS !tv h e>+++ b++
: You can't blame yourself for what gorillas did :: UL++++$ C++ E--- a?

More information about the Mono-devel-list mailing list