[Mono-dev] Static Bundling

[Paolo Molaro]

On 12/18/07 Avery Pennarun wrote:
> I've been looking at using mkbundle myself for my own work.  It's
> network stuff, not graphical, so I wouldn't expect gdiplus to be a
> problem for me.
> 
> But what exactly is "that case" that it can't cope with?
> Dynamically-linked elf libraries?  Could I just rebuild with static
> libs instead?

mkbundle solves the needs of 99% of the people that need it's
capabilities. It doesn't solve all the worlds problems, so you can't
expect it to. From the manpage:
	mkbundle  generates  an  executable  program that will contain static
	copies of the assemblies listed on the command line.
And it does exactly what it's documented to do.

If you need additional capabilities you can roll your own, like
linking the libs to your program yourself and redirecting the p/invoke
calls as explained in man mono-config.

Also, let me take this occasion to remind everyone that statically
bundling the libmono library and any other LGPL library requires (if you
distribute the binary) that you also distribute all the stuff that is
needed by the user to relink your code to a different version of the
library (this is just one of the ways to comply with the license, see
the LGPL for more details).

lupus

-- 
-----------------------------------------------------------------
lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better