5 seconds doesn’t sound that bad to me. Don’t forget that Haxe uses a different compiler to regular as3 projects so it’s likely to take a different amount of time.
I wonder if this is running the “assets.swf” build or not
In the past, we used to run a single SWF build in memory, but this hit some hard (and bad) size limits for large projects. In order to resolve this, assets are now compiled to another SWF separately, then the project is compiled, linking this first SWF.
Another change is that Haxe 3 is slower than Haxe 2, it adds a lot of improvements/safety but lost some gains in the performance department. Not sure if the next release changes this at all.
Third, the OpenFL tools are not currently performance tested, only tested for consistency/accuracy, so there may be some areas that could be improved (they probably are there) to keep things zippy.
What if you do -verbose while you build, does it seem to hang on one thing, or does it seem to zip along pretty consistently?
Thanks for the response. I’m asking because my project reached ~8-12 second compilation time and it kinda breaks the flow if i want to test out something quickly. And with flash projects it takes about 1-3 seconds for larger projects with lots of assets.
Also tested regular Haxe Flash Project. It is as fast as Flash AS3. So it couldn’t be Haxe 3 fault.