On Wed, Aug 13, 2014 at 3:21 PM, Alex Harui <[email protected]> wrote:
> Looks fine to me. Would be finer with an Apache header ;-) > > Argh. Noob mistake ;-) Thanks for guiding me through the solution. Om > On 8/13/14 1:53 AM, "OmPrakash Muppirala" <[email protected]> wrote: > > >I just checked in this functionality. Please do a quick review when you > >get a chance. > > > >Thanks, > >Om > > > > > >On Tue, Aug 12, 2014 at 1:36 PM, Alex Harui <[email protected]> wrote: > > > >> > >> > >> On 8/12/14 11:42 AM, "OmPrakash Muppirala" <[email protected]> > wrote: > >> >>It seems like that would be useful for testing different versions of > >> >> Android in the simulator regardless of this bug. > >> >> > >> > > >> >There is another problem though. I have a mobile app with two > >>run/debug > >> >configurations, one for iOS and one for Android. AIR simulator works > >>fine > >> >for iOS, i.e. it does correctly report "IOS xxx" for version. > >> > > >> >If I add this as a compiler option, it will apply to all run > >> >configurations, right? Is there a way to include a compiler option > >>for a > >> >particular run configuration in FB? > >> Well, you could have the Mixin check the other Capabilities properties > >>and > >> decide whether to apply the override or not. > >> > >> -Alex > >> > >> > >
