Open GoogleCodeExporter opened 9 years ago
I had a quick test the other day at home (I have no internet atm and my mobile
browser is rubbish) and got errors also. I believe this is probably to do with
the new version of haxe as there were no issues previously. I know the new
version of haxe supports multiple -lib operands now and probably means the way
swcs are used has changed slightly too. (I think I remember reading something
about not needing to extract the stub classes with haxe compiler before using
the swc. Probably other changes too)
I should have internet properly in a few days and then i can look up the
changes etc.
Original comment by lucadelt...@googlemail.com
on 30 Aug 2010 at 3:29
It seems this may be a bug in the most recent haxe version in regards to
producing the swc file stopping the swc from working within another haxe
project.
Bugging nicolas about it on the list :P
Original comment by lucadelt...@googlemail.com
on 3 Sep 2010 at 9:40
so, any news on this?
Original comment by thes...@gmail.com
on 27 Sep 2010 at 10:18
Unfortunately no, right now you will still have to use the haxe compilation and
won't be able to use the compiled swc. I had a go at getting around the
apparent problem which was due to conflicts with hx std types. But after
getting around that, all i ended up with was a white screen which still didn't
work.
I'm guessing you are wanting to use the swc to increase compilation speed? It's
a shame but for now there's no choice for haxe.
Original comment by lucadelt...@googlemail.com
on 27 Sep 2010 at 11:25
yes i wanted to increase compilation speed but i also wanted to have a similar
setup both in haxe and as3, by using the same swc.
Do you have any idea why the white screen? Thats doesnt make much sense in
relation to haxe std types
Original comment by thes...@gmail.com
on 2 Oct 2010 at 9:00
Well this issue is that using -swf-lib with the extracted swf from the .swc
causes an error related to the haxe std lib complaining about having an invalid
number of type parameters to IntHash from within the swf. So I decided to
create my own IntHash variant to use in nape to avoid the name clash which has
appeared with new haxe version. But when i did so, I simply ended up with a
white screen with no code executing.
Regarding your reason for wanting swc for having the same setup, this isn't
really a problem with recent versions of nape where every class is in it's own
file now so that the imports needed are the same whether you use the swc or the
source or AS3.
It's a pain that it doesn't work right now regarding compilation speed i know.
Original comment by lucadelt...@googlemail.com
on 4 Oct 2010 at 12:25
Original issue reported on code.google.com by
thes...@gmail.com
on 25 Aug 2010 at 6:06Attachments: