Closed TerryCavanagh closed 8 years ago
Perhaps problem in new openfl? Try openfl 3.3.9 and lime 2.7.0
Ok, I gave that a go!
haxelib set openfl
Version : 3.3.9
Library openfl current version is now 3.3.9
So, I set openfl to 3.3.9: running the following:
openfl build flash -Dlegacy
Now gives a different error:
C:/coding/haxe/haxe/lib/openfl/3,3,9/openfl/utils/ByteArray.hx:5: characters 0-19 : Type not found : lime.utils.ByteArray
Also tried 2.2.4 for good measure, but got the same bug :(
Ah! Just had a breakthrough!
I installed version 2.1.0 of lime as well, and set my lime version to that with:
haxelib set lime 2.1.0
After that I was able to compile the flash version fine. Woo!
For info, I lost my haxe/lib install recently and had to redo, had very similar issues to you, but got working eventually with these lib versions
Haxe Compiler 3.2.1 - (C)2005-2015 Haxe Foundation
actuate: [1.8.6] away3d: git [dev:/usr/local/lib/haxelib/away3d/git] format: [3.2.1] hxcpp: [3.2.193] lime: [2.8.1] openfl: [3.5.1]
However, I can only get C++ targets to work, which is fine as not targeting flash.
Ah, that's interesting - I was only targetting flash, but more long term I'm interested in C++ targets too.
Here's hoping the library gets updated to work with the latest versions of OpenFL at some point!
I'll second that, I've been experimenting with Away3D OpenFL for a few months and been quite impressed, it would be great if it fully supported the latest OpenFL/Lime.
Looks like Away3D just got updated to work on the latest version of OpenFL, which fixes this. Awesome!
I'm unable to compile the current version of away3d with haxe 3.2.1. I followed these steps:
haxelib git away3d https://github.com/away3d/away3d-core-openfl.git
(I installed from github rather than haxelib to work around https://github.com/away3d/away3d-core-openfl/issues/55. If I use the haxelib version on 3.2.1, I get the same error message as in that issue.)
I then installed the basic view example:
On flash:
produces this error:
On HTML5:
Produces this error:
Finally, on windows:
...produces this error:
(Neko worked fine, though!)