Closed GoogleCodeExporter closed 9 years ago
That seems incredibly slow, on my system compiling in debug mode takes about 7
seconds, compiling in release mode about 1 second.
There are some parts of the engine which could be sped up compilation time wise,
however the bulk of the compilation time is spent in the run-time critical
areas of
the engine. The engine takes long time to compile for the same reason that it
runs
extremely quickly.
If it were to be something important, I would consider adding a compiler flag
for
haxe compilation to disable certain optimisations for faster compilation.
Original comment by lucadelt...@googlemail.com
on 4 Jun 2010 at 3:19
If you are targeting the flash platform, you could perhaps try and just use the
compiled .swc instead of the source so you don't need to recompile the engine
every
time you test your application.
Original comment by lucadelt...@googlemail.com
on 4 Jun 2010 at 6:06
>>If you are targeting the flash platform, you could perhaps try and just use
the
>>compiled .swc instead of the source so you don't need to recompile the engine
every
>>time you test your application.
It is possible with haxe?
Original comment by 623...@gmail.com
on 5 Jun 2010 at 7:12
http://haxe.org/doc/advanced/swc, I do believe I can remember on the mailing
list
something about being able to do it directly now or something aswell without
having
to do that faff., though I'm not sure.
Original comment by lucadelt...@googlemail.com
on 5 Jun 2010 at 10:39
Well especcialy now that new version of haxe supports multiple swc files, i
feel this is no longer an issue at all.
Original comment by lucadelt...@googlemail.com
on 21 Aug 2010 at 10:07
Original issue reported on code.google.com by
623...@gmail.com
on 4 Jun 2010 at 3:10