Re: [devel@lists.monobjc.net] iPhone / iPad ?

[Laurent Etiemble]

NB: Please, be sure to subscribe before sending on the list as it is
restricted to subscribers (mainly to avoid the spam).

-- Message transféré --
From: Matt Emson memson.li...@googlemail.com
To: devel@lists.monobjc.net devel@lists.monobjc.net
Date: Thu, 21 Jul 2011 20:37:43 +0100
Subject: Re: [devel@lists.monobjc.net] Re: Delivery to the mailing list [
devel@lists.monobjc.net] failed


Sent from my iPhone 4

On 21 Jul 2011, at 15:18, Erik Touve eto...@sbcglobal.net wrote:

Thanks for all the posts.

So the license part (due to statically linking) is still the major barrier
for the community.


Yes. To static link, you need to buy a commercial mono license. To use the
runtime without a static compilation, it is free, but licensed LGPL, which
will be disallowed from the AppStore. Sorry, I didn't explain properly
earlier.

M


2011/7/21 Erik Touve eto...@sbcglobal.net


 Thanks for the reply.

 I was interested in hearing your thoughts on it.

 Agreed that tools would need a lot of work.  I wasn't aware of the
 licensing issue - which makes development a moot point.

 Sigh.

 --
 *From:* Laurent Etiemble laurent.etiem...@monobjc.net
 *To:* devel@lists.monobjc.net
 *Sent:* Thu, July 21, 2011 7:55:39 AM

 *Subject:* Re: [devel@lists.monobjc.net] iPhone / iPad ?

 Hello,

 There are several points before running Monobjc on an iOS device:
 - Getting Mono to build and run on iOS (feasible with the right switches)
 - Getting the native part of Monobjc to build and run on iOS (one caveat is
 libFFI, but is seems that there is now a support for iOS devices)
 - Be able to link and shrink all the assemblies so the IL code is the
 smallest one (this is the hardest part)
 - Wrapping everything into an executable (this looks like the embedding
 done on the Mac), and link statically with Mono.

 IMHO, the tooling part is the one that requires the heavy work. In
 addition, the last time I took a look, a license was needed to use the
 static linking of Mono.

 Regards, Laurent Etiemble.

 2011/7/18 Erik Touve eto...@sbcglobal.net

 I was wondering if it's possible to wrap the iOS SDK framework in
 monoobjc.

 Unity does an excellent job of mono on iOS.

 I fully support Ximian / Novell / now Xamarin efforts.  I love the .NET
 implementation.  But, I'm not willing for fork over $400 for in-house
 application development - something I'm not ever going to sell through any
 store.

 In theory I suppose monobjc could do the same thing as MonoTouch.  I'm
 certain there's a lot of work connecting all the dots... for example
 specialized mono compilation.

 Are there plans to do this eventually?  Can I do this myself?  Are there
 crazy licensing issues?

 -E

Re: [devel@lists.monobjc.net] iPhone / iPad ?

[Laurent Etiemble]

Hello,

I am reposting the mail, as it was blocked by the lists platform:

-- Message transféré --
From: Victoria French victoria.fre...@metrosharp.co
To: devel@lists.monobjc.net
Date: Tue, 19 Jul 2011 13:11:05 -0500
Subject: Re: [devel@lists.monobjc.net] iPhone / iPad ?
I can't speak for Novel here, but I can tell you that first there would need
to be a very special version of mono made itself. I would have to not only
be compiled to run on Apple A chips but the concept itself needs changing.

Mono would no longer be able to run without being pre-jitted at compile time
to native code (Apples rule on interprereted languages). Then the entire
framework would need to be a static library (.o) instead of a dynamic one
(ex .dylib, .dll) again Apples rule on linking to dynamic libraries.

After all the necessary changes to Mono was completed then Monobj could be
ported but again lies the dynamic linking rule.

I can see why Novell is charging for MonoTouch, the amount of work to make
this a reality is insane. Think if your app had to load the entire mono
library in memory! You would immediately end up with the phone rebooting.
You only get 128M of ram, no paging file and your entire application gets
loaded into that memory space before you can even execute a line of code.

$400 is cheaper than trying to get someone else to do this or even doing it
yourself IMO.

V


2011/7/18 Erik Touve eto...@sbcglobal.net

 I was wondering if it's possible to wrap the iOS SDK framework in monoobjc.

 Unity does an excellent job of mono on iOS.

 I fully support Ximian / Novell / now Xamarin efforts.  I love the .NET
 implementation.  But, I'm not willing for fork over $400 for in-house
 application development - something I'm not ever going to sell through any
 store.

 In theory I suppose monobjc could do the same thing as MonoTouch.  I'm
 certain there's a lot of work connecting all the dots... for example
 specialized mono compilation.

 Are there plans to do this eventually?  Can I do this myself?  Are there
 crazy licensing issues?

 -E