IntelliJ: Flex Compiler Shell (fcsh) is good for small projects, and may be useful in large projects as well, when you need to compile only some of the modules (facets). Fcsh process is kept in memory between compilations, so it is able to quickly recompile only changed piece of code (that is called incremental compilation), but in case of large projects fcsh runs out of memory, then IntelliJ IDEA restarts it automatically, but incremental compilation data is lost.
Mxmlc/compc processes are not kept in memory between compilations, but simultaneous running of independent compilations gives a good performance gain. IntelliJ IDEA automatically finds independent compilations based on module-on-module dependencies, configured in Project Structure (Ctrl+Alt+Shifl+S), Modules node, Dependencies tab. Randori: In Randori I track the modified files and passed them as "include-source" parameter to the compiler to make incremental compilation, I don't what Mike S. did behind the scene to make it work though but the source code is opened. -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mercredi 4 septembre 2013 19:48 À : Erik de Bruin Cc : dev@flex.apache.org Objet : Re: [Falcon] BasicTests compiles and runs On 9/4/13 10:43 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >Might we be able to get someone on the Flash Builder team (if there is >such a thing) to join this conversation and maybe shed some light on >some of these issues? I believe the original authors are no longer at Adobe. It is interesting that folks using IntelliJ don't complain about compile time issues yet IntelliJ doesn't use incremental compiles. It makes me wonder whether all of that incremental compile code is truly needed or whether there is something about Eclipse that gets in the way. I keep hoping someone out there has Eclipse plug-in expertise and can say "oh yeah, here's a quick way to build a new "builder" or code model extension. -Alex
