Someone has used Haxe/Openfl/Lime with raspberry pi, I have had success with installation at haxe and openfl but, with lime… nothing.
I have this output after installation:
haxelib run lime setup
Called from lime/utils/ByteArray.hx line 108
Called from lime/system/System.hx line 221
Called from lime/system/System.hx line 323
Called from lime/system/System.hx line 164
Called from neko/Lib.hx line 30
Uncaught exception - load.c(237) : Failed to load library : lime.ndll (lime.ndll: cannot open shared object file: No such file or directory)
thanks in advance
I’m not fully sure of the current status for Raspberry Pi, as it’s not officially supported, but I know that the binaries for it are not included. You would need to use lime rebuild linux -Dlegacy -Drpi on a Raspberry Pi system to try and rebuild
the system starts, but stops with :
./…/legacy/project/src/sdl/SDLStage.cpp: In member function ‘virtual const char* nme::SDLStage::getJoystickName(int)’:
./…/legacy/project/src/sdl/SDLStage.cpp:695:41: error: ‘SDL_JoystickNameForIndex’ was not declared in this scope
Singmajesty, Where can I see more details about OpenFL and Raspberry?
Oh… just this week, we moved to a snapshot version of the Lime “legacy” code to lock it down (we were previously relying on a shared codebase that’s moving in a different direction). The Raspberry Pi support was using SDL1, we currently do not use SDL1 in any platform, except for the BlackBerry target – but that use a custom port that we keep precompiled.
Long-story short, we’re not building SDL1 anymore, as we moved everything else to SDL2. I wonder if SDL2 supports Raspberry Pi?
Based on some initial searching around, I think that SDL2 can work with Raspberry Pi. In that case, I think it may make sense to modernize the support – it’s probably almost the same as standard Linux support, with a couple tweaks, as far as the Lime layer is concerned.
Depending on your needs, there is the new Lime API, and the Lime “legacy” binary. You can see the source (are you very familiar with C++?) in either “lime/project/src” or “lime/legacy/project/src”. Between the two, you might find the newer code easier to see, and it might be easier to adapt for Raspberry Pi if it works with SDL2.
If there’s a compelling reason, we might also look at officially supporting RPI, so if you have any information on why it would be good to support, would be nice as well 
There’s now a Tizen image for the new Raspberry Pi if it helps.
