[Mono-dev] How can I build a minimal mono runtime system?
stapostol at gmail.com
Tue Dec 21 09:03:13 EST 2010
There is a very simple solution to this: build everything but deploy only
the dlls that you need. Use mono-linker to find out which dlls you are
linking against, so if you don't need System.Net.dll, System.Data.dll, etc,
keep them out.
I am using this approach for a game. The Mono runtime fits in just 4MB
7zipped (this includes support for Linq, XML and System.Drawing without
libgdiplus.so) and I am embedding the runtime into a trivial, native
launcher. Everything is working perfectly so far!
2010/12/21 CodeSlinger <dkolb at emdeon.com>
> I have to respectfully disagree that being able to remove major subsystems
> that one does not need at all is fluff - major components such as the
> compilers, the GUI and ALL of the web components instead of just moonlight.
> Some of the current "--with/--enable" options, esp. some of the
> "--enable-minimal" choices that are there, feel much more fluffy and are
> often even advised to not be used. I'm not looking to remove at a small
> granularity stuff like generics, or debugging or decimal features, just
> whole subsystems. You either need the web stuff or not. The GUI stuff or
> not. Something akin to the V4 client framework might also make sense. There
> are a lot of small Linux systems and a lot of Linux'es used without GUI
> since they are used as servers. It would help if I knew what all the .dll
> modules were so I guess I try to figure that out next so I can remove a
> bunch of them for a minimal copy to our prod system. My .02
> View this message in context:
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list