Hi, It's definitively possible to add support for AOT in the simulator, it's just a matter of priorities, for now there are more important things to add/fix before adding support for this.
Rolf On Thu, Jan 12, 2012 at 5:10 PM, Demis Bellot <[email protected]>wrote: > If its just a case of being optimized, it sounds like it should still be > runnable with AOT in the simulator? > Any chance of making this (non-default) option available? > > > On Thu, Jan 12, 2012 at 9:39 AM, Rolf Bjarne Kvinge <[email protected]>wrote: > >> Hi, >> >> On Wed, Jan 11, 2012 at 8:35 AM, René Ruppert < >> [email protected]> wrote: >> >>> Why don't you offer AOT for the Simulator btw? >>> >> >> Because compiling using AOT is (significantly) slower, which means that >> the edit-run-debug cycle is slower. In short, we've optimized the simulator >> experience for debugging your app, while the device experience is tuned for >> execution speed. >> >> Rolf >> >> >>> >>> Grüße, René >>> >>> Am 10.01.2012 um 22:29 schrieb Rolf Bjarne Kvinge <[email protected]>: >>> >>> Hi Demis, >>> >>> Unfortunately the only way right now is to compile for device, and see >>> which errors show up. If you file a bug report with test cases, we can look >>> into fixing specific cases. >>> >>> Rolf >>> >>> On Tue, Jan 10, 2012 at 10:26 PM, Demis Bellot >>> <[email protected]>wrote: >>> >>>> (for instance there is no way to detect Ahead-of-Time compilation >>>>> issues with the simulator) >>>> >>>> >>>> Yeah that's what's failing, Getting unknown exceptions (due to heavy >>>> use of generics) I just need to track where this bad boy is. >>>> >>>> Cheers, >>>> >>>> >>>> On Tue, Jan 10, 2012 at 4:17 PM, Rolf Bjarne Kvinge >>>> <[email protected]>wrote: >>>> >>>>> Hi, >>>>> >>>>> Exactly what is failing? Depending on the failure, there might be >>>>> things you can do (if it's a linker failure, you can turn on linking for >>>>> simulator builds, if you're targetting a specific iOS version, you can >>>>> select the version of the simulator to run against, etc.) There are >>>>> however >>>>> a lot of cases that will still be different (for instance there is no way >>>>> to detect Ahead-of-Time compilation issues with the simulator) >>>>> >>>>> Rolf >>>>> >>>>> On Tue, Jan 10, 2012 at 7:31 PM, Demis Bellot >>>>> <[email protected]>wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Is there an easier way to test iOS restrictions without running in on >>>>>> the device? >>>>>> I have some code passing on the simulator but failing when running on >>>>>> the device. >>>>>> >>>>>> Curious is if there's some flags we can a Console app on that best >>>>>> simulates the restrictions on iOS devices? >>>>>> >>>>>> Cheers, >>>>>> >>>>>> _______________________________________________ >>>>>> MonoTouch mailing list >>>>>> [email protected] >>>>>> http://lists.ximian.com/mailman/listinfo/monotouch >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> - Demis >>>> >>>> http://twitter.com/demisbellot >>>> http://www.servicestack.net/mythz_blog >>>> >>>> >>> _______________________________________________ >>> MonoTouch mailing list >>> [email protected] >>> http://lists.ximian.com/mailman/listinfo/monotouch >>> >>> >> > > > -- > - Demis > > http://twitter.com/demisbellot > http://www.servicestack.net/mythz_blog > >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
