What's the difference between --aot=full and mkbundle? --aot=full looked
like it should produce a single binary as well..
--aot=full merely compiles all the code natively, much more than regular
--aot does, including all sorts of extra methods that the engine believes
you might need.
This
I've got a C# project that I need compiled to a native binary. I've read here
on the AOT page that Mono can precompile an assembly to one of two options:
--aot : A precompiled image (essentially the same as Ngen as it looks to me)
--aot=full: A fully compiled to native binary instance of the
On Mon, Nov 7, 2011 at 11:15 AM, applepi chrisdd...@gmail.com wrote:
I've got a C# project that I need compiled to a native binary. I've read here
on the AOT page that Mono can precompile an assembly to one of two options:
--aot : A precompiled image (essentially the same as Ngen as it looks
Slide wrote:
On Mon, Nov 7, 2011 at 11:15 AM, applepi lt;chrisddail@gt; wrote:
I've got a C# project that I need compiled to a native binary. I've read
here
on the AOT page that Mono can precompile an assembly to one of two
options:
--aot : A precompiled image (essentially the same as
On 07.11.2011 19:34, applepi wrote:
I'd not seen mkbundle. I'll have to look into that as well.. this is going
into proprietary code for a customer and I'm not as brushed up on how all of
the GPL/LGPL restrictions affect that as I should be, so I'll have to dig
into that somewhat.
You
Robert Jordan wrote:
On 07.11.2011 19:34, applepi wrote:
I'd not seen mkbundle. I'll have to look into that as well.. this is
going
into proprietary code for a customer and I'm not as brushed up on how all
of
the GPL/LGPL restrictions affect that as I should be, so I'll have to dig
Full AOT just means that absolutely everything will be precompiled,
including things which may negatively affect performance or binary size.
This is only useful for platforms which explicitly disallow jitting such as
iOS. Even should full AOT be supported on the desktop (and it's not
supported
