Skip to main content
Participating Frequently
August 27, 2013
Question

Compilation never ends

  • August 27, 2013
  • 1 reply
  • 1273 views

I tried to compile my project for iOS devices (adt.exe tool), but compilation lasts forever (I waited many hours).

Only one swf (3Mb, using Starling framework). The same swf compiles in 20 seconds for Android or Windows package.

I tried different package options, different java versions, different computers (Windows 7, AIR3.8beta), the result is the same: I see java.exe in processes, but nothing happens. I see AOTBuildOutput1234.tmp with files, but modification date stays the same for them.

Is there any way to understand what's happening?

This topic has been closed for replies.

1 reply

Inspiring
August 27, 2013

First and foremost, compiling for iOS takes a lot of resources, it cannot be compared to packaging for Android, because the process is completely different, AIR on Android runs interpreted code, while on iOS it is native code, before deciding the compilation is stuck you should check the java/adt processes aren't doing anything. It's been said future AIR versions will reduce iOS compilation times.

Second, I've seen iOS compilation fail and take forever only when using certain ANEs and Flash Builder versions. FB doesn't take too well certain ANE warnings and errors, and instead of ignoring or finishing the process showing some alert, it just sits there making you wait forever. If you are using ANEs in your project, you should isolate the problematic one, and then determine what may be the cause... if some problem with the iOS SDK used with your AIR SDK, if the ANE is causing some unimportant warnings but your IDE doesn't like them, etc.

DiamanterAuthor
Participating Frequently
August 28, 2013

Thank you!

No, I'm using one swf (no extensions, no additional resources, I removed even icons from adt call).

I decided it's stuck because files in AOTBuildOutput stop changing (they are changing only first 3 minutees of the compilation). Process java.exe continues to work, it takes one core 100% and eats some memory, but no new output during next 10 hours.

Adobe Employee
August 28, 2013

Could you please log a bug at bugbase.adobe.com, with your swf, app xml and sources if possible.

Meanwhile, few questions -

1. How was the swf compiled - using FB? Which version? and which AIR SDK version?

2. Does your AS code contain any extremly big functions (of the order of thousands of lines)?