|Subject:||Re: Live GNUstep Android game ( Golf Blitz )|
|Date:||Tue, 7 May 2019 22:06:01 +0200|
|Congratulations on the release, really great to see GNUstep used in the wild like this!|
As we’ve also been working on an GNUstep Android toolchain (announcement forthcoming by Greg Casamento), I’d love to see if we can somehow combine our efforts towards making GNUstep work great on Android.
Our solution to managing the build process has been a collection of concise scripts, one for each library, to pre-build the toolchain into a common shared location (for all ABIs). An Android project can then integrate the toolchain by calling gnustep-config in that location to get the necessary compiler/linker flags (e.g. from CMake as shown in our Android Studio example project).
Other than that our setup seems very similar (e.g. using libdispatch and ARC), but it’d be great to hear where it differs from yours. We also have an integration with Qt internally (including integrating libdispatch with the Qt run loop) which I hope to share as another example.
While we’re still a long way from shipping something with this setup we’re pretty happy with our early prototypes using it.
As a side node, as of today the toolchain also works on arm64 and x86/x86_64 (great for using the emulator) using the gnustep-1.9 runtime (we tried using the 2.0 runtime but ran into an issue with the clang version that is part of the NDK, but hopefully we can make the switch with a future NDK release).
Am 04.05.2019 um 05:49 schrieb Jordan Schidlowsky <address@hidden>:
|[Prev in Thread]||Current Thread||[Next in Thread]|