Skip to main content
J
JonathanKaye19147
Inspiring
December 17, 2014
Answered

A clarification on the compiler for iOS universal support

  • December 17, 2014
  • 1 reply
  • 683 views

Hello, I saw in the release notes for AIR 16 and the new iOS universal support we will need to use the new compiler, I assume that means "-useLegacyAOT no". I tried compiling my app with AIR 15 and got some weird errors, so I set "-useLegacyAOT yes" and it worked properly. I have a question whose answer would help me a lot.

Can I continue NOT to use the ASC 2.0 compiler, or must I use it in the future as I set -useLegacyAOT to no?

Thank you!

-jonathan


This topic has been closed for replies.
Correct answer Govind11519869

Hi Jonathan,

“new compiler” here mean “new AOT Compiler”.

Please continue to use ASC 2.0 compiler to create swf files. It is better than ASC 1.0

AIR 15 doesn’t have universal IPA support. You need to use AIR 16 for the same. AIR 16 have only new AOT compiler and “-useLegacyAOT” is not honoured anymore.

Hope that answers your queries.

Thanks

Govinda Gupta

1 reply

G
Adobe Employee
Govind11519869Correct answer
Adobe Employee
December 18, 2014

Hi Jonathan,

“new compiler” here mean “new AOT Compiler”.

Please continue to use ASC 2.0 compiler to create swf files. It is better than ASC 1.0

AIR 15 doesn’t have universal IPA support. You need to use AIR 16 for the same. AIR 16 have only new AOT compiler and “-useLegacyAOT” is not honoured anymore.

Hope that answers your queries.

Thanks

Govinda Gupta

J
JonathanKaye19147Author
Inspiring
December 18, 2014

Hi Govinda, thanks for the quick reply. I would like to use the ASC 2.0 compiler, but at the time of AIR 4.0, I was getting a few errors when I tried, so I stayed with ASC 1.0 (for example, it flagged my use of someObj.default, I guess I would have to change it to someObj["default"]). When I tried using ASC 1.0 and AIR 15 (leaving the default -useLegacyAOT no), my iOS app was crashing with an unusual error before reaching the first line of the program during debugging, so it seems like an incompatibility in assembling the SWF. I will go ahead and try to fix the errors to get the ASC 2.0 compile to work, then I can see if AIR 15 and 16 will result in a clean build.

Thanks again, and of course thanks for you and your team's hard work!

-jonathan

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices