[Mono-list] Mono embedding issue

Massimiliano Mantione massi at ximian.com
Thu Oct 12 10:33:21 EDT 2006

On Thu, 2006-10-12 at 13:13 +0200, Andreas Färber wrote:
> That's a great hint! Using a user-specific prefix it won't be able to  
> access /usr/bin.

You meant "damage": it can _access_ /usr just fine, and it will happily
use the libraries under /usr/lib...

> What about Mono's dependencies? Is it sufficient to have Mono  
> installed, or do I need additional glib and pkg-config stuff? Any  
> other command line arguments or environment variables necessary for  
> it to find the headers and libraries?

...and this is why you do not need to duplicate the dependencies.
Your new Mono will use your existing glib and pkg-config.

However, I strongly suggest you to update all the three env vars
(PATH, LD_LIBRARY_PATH and PKG_CONFIG_PATH) when you use your own
custom Mono, as I described in the previous message.
In particular, setting PKG_CONFIG_PATH will allow other components
that need Mono to be built against the custom one.
For instance, if you need gtk-sharp, you should rebuild it (and
reinstall it) using the custom prefix, and in an environment with
the three paths updated.
This will still use the "standard" gtk+ libraries in your system
(as "standard" as gtk+ can be on OS X, but you get the idea), but
the Mono assemblies will be built with the new Mono, and installed
in its GAC in the custom prefix, so that every app using the custom
Mono will find them.

This (correctly installing in the custom prefix) should be done for
each assembly/library/component you need that _depends_ on Mono.
The three env vars make sure that the custom paths have precedence
over the standard ones.

I hope I clarified how the system should work...


More information about the Mono-list mailing list