On 13/03/2017 7:48 PM, Joakim wrote:
On Thursday, 9 March 2017 at 10:35:18 UTC, dummy wrote:
On Wednesday, 8 March 2017 at 10:24:24 UTC, Joakim wrote:
On Tuesday, 7 March 2017 at 12:06:48 UTC, dummy wrote:
Just thought. I do want to know. :-)
As far as I know is,
* LDC2 woring on NDK(yah!)
* Native OpenGLES:
http://wiki.dlang.org/Build_LDC_for_Android#Build_a_sample_OpenGL_Android_app_ported_to_D
* Dlangui working on Android that based on SDL2:
https://github.com/buggins/dlangui /
https://dlang.org/blog/2016/10/07/project-highlight-dlangui/
regards,
Yes, though I have not tried SDL2 myself.
https://forum.dlang.org/post/hbumubsbrzffvgria...@forum.dlang.org
Ah, you're right.
I will trying DerelictSDL2.
Thx :-)
Regarding the link to that forum post, that bug has since been found and
fixed.
If you're planning on using Derelict, there is an issue where all
Derelict libraries are loaded as shared libraries, whereas the Android
port currently doesn't support loading shared libraries. If DLangUI is
using SDL2, maybe he has a header file that allows him to statically
link against SDL2, which you could reuse.
Otherwise, you may need to generate one using DStep:
https://github.com/jacob-carlborg/dstep
or modify the DerelictSDL2 files to allow you to link statically.
Why exactly doesn't the Android port support dlopen, dlsym and dlclose?
It is provided by the NDK libc.
At least according to this[0].
[0] https://developer.android.com/ndk/guides/stable_apis.html
