The main issue is, as suggested, that ASC2.0 is not certified to compile MXML,
only AS.
If it worked in Ant, I’d guess you loaded the Flex SDK’s ant tasks which would
run the Flex SDKs compiler.
-Alex
From: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
Reply-To: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
Date: Saturday, October 25, 2014 at 6:23 AM
To: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Which AIR SDK to use with Flex?
Mark, thanks for the reply.
I don't use Flex builder, just Apache ant and the Flex and AIR SDKs. I was able
to build the Flex/iOS app with both versions of the 15.0.0.302 SDK in their
default configurations, so I guess the one with the new compiler uses the old
one by default. (At least from the command line.) I'm going to stick with the
SDK without the new compiler though, just to be on the safe side.
On Saturday, October 25, 2014 9:39 AM, 'Mark R. Jonkman'
mark.jonk...@comcast.netmailto:mark.jonk...@comcast.net [flexcoders]
flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com wrote:
I’m guessing it mostly has to do with mxml compiling. The old compiler would
have to handle both types of input – ActionScript and MXML and generate
ActionScript code based on the MXML and then generate the final product. If
your Adobe and you no longer support MXML yourself then there is no reason to
keep it around in future generations of the compiler – especially where speed
becomes an issue.
I hit a lot of problems this week with the new fast compiler. AIR SDK 15
switched from using the legacy compiler to the new fast compiler as its default
compiler. My project uses just a small portion of the FLEX framework – just
enough stuff to connect with the backend server running BlazeDS and sending
stuff over AMF. As a matter of fact we actually put the classes we used into
our own project and as far as we knew, no longer linked against any of the Flex
framework SWCs. However after the switch to the new AIR SDK 15 the project
started blowing chunks. It would not find about 8 interfaces and classes from
the Flex framework. Eventually I traced it down to possible being the swc
cache that Flash Builder stores in the workspace .metadata folder (I think). I
deleted all the files in the swc cache and the errors finally went away. It
took hours to track that down. Then I finally got the project compile into an
iOS IPA file and installed it on my iPad – crash after a few seconds of
running. AIR simulator no problem, iOS Simulator no problem. But a debug or
release runtime and crash.. Then I realized that they had changed the default
compiler to the fast, switched back to the legacy AOT compiler and everything
worked perfectly.
Unfortunately if iOS is your target you have almost no choice but to upgrade to
AIR SDK 15. Apple changed the requirements for uploading and all the old SDKs
will not produce an IPA that will be accepted (unless you experiment with
changing the linker and that sounded more like Voodoo then a long term
solution). And the AIR SDK must be the one from at least Oct 14, 2014.
If you did not already know – The AIR SDK is located in two places one is the
Flash Builder 4.7/eclipse/plugin folder (Used by ActionScript projects) and the
other is in the Flash Builder 4.7/sdks folder. The plugin folder is for
ActionScript only projects and the other in the sdk folder is for Flex
projects. At least as near as I can determine.
I would download the default AIR SDK to use with any ActionScript projects –
it’s the SDK that gets put into the eclipse/plugin/actionscript compiler….
Location.
For Flex projects, download the alternative and drop it into the sdks/4.6.0
folder in Flash Builder.
This way you have both compilers setup and useable based on the type of project
your working on.
If you hit the same situation I did with iOS output, then on the project
settings, iOS settings – click customize launch button, click add parameter,
enter –useLegacyAOT for name and for value enter yes. Then click the before..
radio button and choose –provisioning_profile (or something like that). I don’t
have my work computer open so I might be off on a couple of name of the before
radio button and the entery in the drop down list – but it’s the only entry
with provision profile or similar in the name.
Sincerely
Mark R. Jonkman
From: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
[mailto:flexcoders@yahoogroups.com]
Sent: Thursday, October 23, 2014 12:40 PM
To: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Which AIR SDK to use with Flex? [1 Attachment]
[Attachment(s)https://us-mg6.mail.yahoo.com/neo/launch?.rand=4d328m9fkp613#TopText
from Dave