|
Viewing 1 to (224 Total) |
|
some gameplay video of the little thing i'm working on when i get a spare moment.
Posted on April 22, 2013 at 8:37 AM
|
|
so the nme i built from source doesn't work with neko:
Called from native.display.BitmapData::$statics line 644
Called from native.Loader::load line 63
Called from neko.Lib::load line 33
Uncaught exception - load.c(352) : Primitive not found : ./nme@nme_bitmap_data_flood_fill(4)
any thoughts?
Posted on April 21, 2013 at 4:44 PM
|
|
ok I downloaded r8e and overwrote the old r8b, and now i don't get the error.
Posted on April 21, 2013 at 3:51 PM
|
|
looks like nme installed r8b but there's newer versions, including the fix below. so i'll try to manually install a new ndk and hope that it actually works  http://developer.android.com/tools/sdk/ndk/index.html...
google searching around:
http://mirror.yongbok.net/pub/linux/android/repository/ndk/docs/CHA...
- ARM: Removed warning when binutils-2.19/ld links prebuilt object by newer binutils-2.21
which reads
Unknown EABI object attribute 44
The reason is that all prebuilt crt*.o and C++ STL are built with later GCC 4.6/binutils-2.21
and contain new tag "DIV_use" with value set to "Not allowed". This tag can be safely ignored
by the original GCC4.4.3/binutils-2.19 toolchain since it is only for sanity check.
Posted on April 21, 2013 at 3:07 PM
|
|
also, i did "haxelib run nme rebuild android" and then got
/opt/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: Warning: /opt/android-ndk/platforms/android-5/arch-arm/usr/lib/crtbegin_so.o: Unknown EABI object attribute 44
Posted on April 21, 2013 at 3:04 PM
|
|
so "setup" still doesn't work for me
but
> Then try "haxelib run nme rebuild linux"
is successfully invoking g++ so far... hasn't finished yet...
ok it completed. no errors. i guess that is good?
!!!!!!!!!!!!!!! UPDATE: when i run i do get problems!
Could not find primitive nme_bitmap_data_flood_fill__4.
Could not find primitive nme_font_register_font__2.
Could not find primitive nme_font_iterate_device_fonts__1.
Posted on April 21, 2013 at 11:55 AM
|
|
thank you for persisting, sorry i have the world's worst midas touch with computers. it only means i shoulda been in qa.
(seems to me since there's the "primitive not found" error it is not just due to not using sudo.)
superman@superlap:~/Dev/nme-all/NME$ sudo haxelib run nme setup
[sudo] password for superman:
Called from native/display/BitmapData.hx line 644
Called from native/Loader.hx line 63
Called from /usr/lib/haxe/std/neko/Lib.hx line 33
Uncaught exception - load.c(352) : Primitive not found : /usr/lib/haxe/lib/nmedev/git//ndll/Linux/nme@nme_bitmap_data_flood_fill(4)
superman@superlap:~/Dev/nme-all/NME$ which haxe
/usr/bin/haxe
superman@superlap:~/Dev/nme-all/NME$ haxe
Haxe Compiler 2.10 - (c)2005-2012 Motion-Twin
superman@superlap:~/Dev/nme-all/NME$ haxelib list | grep nme
nmex: [1.0.3]
nmedev: git [dev:/usr/lib/haxe/lib/nmedev/git]
nme: 3.5.5 [dev:/home/superman/Dev/nme-all/NME]
Posted on April 21, 2013 at 11:53 AM
|
|
superman@superlap:~/Dev/nme-all/NME/tools/run-script$ haxe RunScript.hxml
superman@superlap:~/Dev/nme-all/NME/tools/run-script$ cd ..
superman@superlap:~/Dev/nme-all/NME/tools$ cd ..
superman@superlap:~/Dev/nme-all/NME$ haxelib run nme setup
Called from ? line 1
Called from CommandLineTools.hx line 969
Called from CommandLineTools.hx line 1211
Called from utils/PlatformSetup.hx line 436
Called from utils/PlatformSetup.hx line 496
Called from utils/PlatformSetup.hx line 357
Called from /usr/lib/haxe/std/neko/_std/sys/io/File.hx line 69
Called from /usr/lib/haxe/std/neko/_std/sys/io/File.hx line 60
Uncaught exception - [file_open,/usr/lib/haxe/nme]
superman@superlap:~/Dev/nme-all/NME$ cd tools/command-line
superman@superlap:~/Dev/nme-all/NME/tools/command-line$ haxe CommandLine.hxml
superman@superlap:~/Dev/nme-all/NME/tools/command-line$ cd ..
superman@superlap:~/Dev/nme-all/NME/tools$ cd ..
superman@superlap:~/Dev/nme-all/NME$ haxelib run nme setup
Called from native/display/BitmapData.hx line 644
Called from native/Loader.hx line 63
Called from /usr/lib/haxe/std/neko/Lib.hx line 33
Uncaught exception - load.c(352) : Primitive not found : /usr/lib/haxe/lib/nmedev/git//ndll/Linux/nme@nme_bitmap_data_flood_fill(4)
Posted on April 21, 2013 at 11:35 AM
|
|
i wish that instead of .zips and instead of the (as far as i can tell) not-working instructions (which ever ones you happen to choose, there are so many different instructions) for how to build from git source, i wish there was a variant of the install script that installed the development build. so it would be like the .zip but an installer program instead. in the hopes that it would somehow work better than the other 2 options which i cannot get to work for me at all.
(are there any people who are running haxe 2.10 on linux and e.g. actually can get the 3.6 or 4.0 zips to work for their project? i've always gotten / seen sound errors.)
Posted on April 21, 2013 at 11:29 AM
|
|
(so for posterity i'd like to point out something, that the problem people have -- apparently -- when they write docs (i've written docs and committed the same offenses!!) is that they fail to explain all along the way what the correct current state of the system should be. the reader cannot fathom things like: which nme directory should be set. or precisely what directory they should be in. that kind of stuff. oh well.)
Posted on April 21, 2013 at 11:26 AM
|
|
the other other other problem is that what you said about bulding command line tools also doesn't work for me:
(a) if i already set dev to the git clone, i get the "Invalid module : run.n thing"
(b) if i use my from-installer nme 3.5.5, i get: "This command can only be run from a development build of NME"
(c) if i cd into tools/command-line and do "haxe CommandLine.hxml" then the first time i tried it i got the errors below [1]. i mucked around some more with (a) and (b) and stuff and now for some reason it actually succeeded in building. so anyway the instructions, all the instructions i've ever seen pretty much, utterly fail to explain the right way to get this to work as far as i can tell.
(d) well, even after CommandLine.hxml worked, i guess that was just a red herring because when i try setup again it fails
superman@superlap:~/Dev/nme-all/NME$ haxelib run nme setup
Uncaught exception - load.c(393) : Invalid module : run.n
[1] errors:
superman@superlap:~/Dev/nme-all/nme/tools/command-line$ haxe CommandLine.hxml
../helpers/LogHelper.hx:5: characters 0-18 : Class not found : nme.Loader
src/CommandLineTools.hx:603: characters 3-18 : #LogHelper has no field error
src/CommandLineTools.hx:608: characters 3-17 : #LogHelper has no field info
src/CommandLineTools.hx:643: characters 5-20 : #LogHelper has no field error
src/CommandLineTools.hx:469: characters 4-18 : #LogHelper has no field warn
src/CommandLineTools.hx:487: characters 3-17 : #LogHelper has no field info
/usr/lib/haxe/lib/xfl/1,04/format/xfl/dom/DOMDocument.hx:8: characters
0-18 : Class not found : nme.Assets
<and a zillion more>
Posted on April 21, 2013 at 11:24 AM
|
|
the next problems i have, are that the Git README instructions
(1) say haxe 3 is required, which implies it won't work with 2.10 (but i have not installed haxe 3 anyway)
(2) they just don't work, as far as i can tell:
superman@superlap:~/Dev/nme-all/NME$ haxelib dev nme $PWD
Development directory set to /home/superman/Dev/nme-all/NME
superman@superlap:~/Dev/nme-all/NME$ haxelib run nme setup
Uncaught exception - load.c(393) : Invalid module : run.n
others have reported that same problem before more than once i think, if you look through search results
Posted on April 21, 2013 at 11:13 AM
|
|
the first problem i have is that i fear you are missing my point about how there is a "from source" contributed page on this site that is out of date, wrong, misleading, unhelpful, just plain trouble -- can i just delete it outright?????????? it shows up in google etc. searches and is just evil.
http://www.nme.io/developer/contributions/source/...
Posted on April 21, 2013 at 11:00 AM
|
|
see for example the intel propaganda, and others:
http://software.intel.com/en-us/android...
http://www.androidcentral.com/tags/intel...
http://phandroid.com/2012/04/18/first-intel-based-android-smartphon...
Posted on April 20, 2013 at 6:42 PM
|
|
thank you i will try that, yessir!!
please then delete the part of the "from source" that tells people to use the development .zip builds!!!!!!!!!!!! or put in a warning about how 3.6 and 4.0 currently do not work????????
i will try from source, but the git readme tells me i have to have haxe 3 and also the last time i tried from git, things utterly did not build out-of-the box, so i wasn't even going to try. i really truly will try again when i get a chance tonight at 2am or something (no free time) and report back!
Posted on April 20, 2013 at 1:01 PM
|
|
thanks for the super details!
if these are the right current accurate correct working details, then pretty please over-write the ones on the "from source" contributed wiki page here on nme.io, because it is just misleading as it currently stands.
or tell me they are right and i can do the edit myself i just don't want to put wrong stuff up more/again.
thank you.
Posted on April 20, 2013 at 12:58 PM
|
|
thanks for the note. (just to double check and clarify -- it isn't just the emulator, it is the actual mobile devices with intel cpus that i care about . the way you wrote things it sounds like you are only thinking about the emulator per chance, but i figure what you mean is intel android devices in general, either real ones or software ones.)
Posted on April 20, 2013 at 12:56 PM
|
|
hi, does anybody know if (a) nme supports android x86 cpus and (b) if yes then where are instructions for it, especially on linux??? i've googled to no avail... hopefully there's something simple that i'm just missing but i worry that i'm not missing anything because when i do "nme help" it only shows arm-5 and arm-7 for android 
Posted on April 19, 2013 at 2:21 AM
|
|
hey so somehow i think i managed to get nme to build from source, i applied the fix per the bug report comments, and rebuild android, and i think now i'm successfully working with soundfx whereas before it was crashing. so this sure seems like a valid important fix to me. is it in later builds? will it go into later builds?
looking athttp://github.com/haxenme/NME/blob/master/project/android/AndroidSo... i see that it is fixed there, yay! so why does the bug report get marked as not fixed?!?!?! scary stressful misleading confusing.
of course, i have no idea how to get anything out of git that can build with/for haxe 2.10, so i dunno how much value there is for me in the fact that it is fixed in git. i suspect it will be a while yet before a dare brave the attempt to switch to 3.0 based on what i've seen in the mailing list.
Posted on April 19, 2013 at 2:05 AM
|
|
why no linux or flash or html or mobile builds -- if there's only mac + windows, i can't try the game out though i watched the youtube video and continue to be amazed.
Posted on April 19, 2013 at 1:59 AM
|
