[Mono-dev] Application deployment questions

Robert Jordan robertj at gmx.net
Fri Aug 25 05:25:08 EDT 2006


> Originally I use Mono-1.1.13, and now I switch to use Mono-1.1.16. I tried
> to use mkbundle.exe but exceptions throw.
> Sources: 1 Auto-dependencies: False
>    embedding: D:\test\x.exe
> Compiling:
> as -o temp.o temp.s
> Unhandled Exception: System.ComponentModel.Win32Exception: Cannot find the
> specified file
>   at System.Diagnostics.Process.Start_shell

Mkbundle requires cygwin for the build process.
You should go to http://www.cygwin.com/ and install
at least the base packages together with "binutils",
"gcc", "gcc-mingw".

After the installation just open a bash shell window,
expand the PATH to point to the Mono installation's bin
folder and invoke mkbundle.

> One restriction on me is that I can't afford to pack all binaries in /bin
> with my application because the overall package size must be limited. I'd
> only utilize a small portion of Mono binaries so that I hope I could pack up
> the only DLLs required with my application.
> I've wrote a simple program and managed to run on a WindowsXP PC which has
> no Mono/.NET installed.
> The DLLs required are as following: iconv.dll, intl.dll, libglib-2.0-0.dll,
> libgmodule-2.0-0.dll, libgthread-2.0-0.dll, mono-1.dll, and mono.exe.
> Would the DLLs required in Linux and MacOSX be different than in Win32?

Glib is usually installed on Linux, so only libmono.so is required.
For MacOS all those libs need to be deployed.


More information about the Mono-devel-list mailing list