1 person found this helpful
I looked into the slowness of the mxmlc compiler , because it does get slow when you have a big project. I stumbled across the fcsh (Flex Compiler Shell). The documentation states that it can be faster than mxmlc because it skips over launching the jvm and it keeps everything in memory for future compilations. I don't know how this fits into your development process ( hello shell-scripting ) , but it is worth a gander
If this post was helpful , please mark it as such.
Here is the link.
You can also try modularizing your application (e.g., several different .swc libraries supporting a main application). In this case, you may not need to rebuild all the pieces every time, saving your some time. Or the "-incremental=true" option.
Yes I already did that. The problem is that flex often recompile the whole project anywa. Event if I had split the project into separated libraries.
And when I want to make a release of my project, it takes 5, 6 minutes !
We are 7 devellopers working on this project, you can imagine the time we lost per day ...
I would like to know if it's worth to buys computers more powerfull but it seems that it's impossible to use the full power of a computer.
Are we condamned to wait so much when compiling event if we have powerfull computers ... ?
I'd look at incremental compiles and fcsh, the compiler shell. You *could*, theoretically, try to profile mxmlc (with something like VisualVM) and try to fix hot spots, but that seems like diminishing returns.
It seems that incremental helps a lot to compile more quickly.
Thanks for the tip