[discussion] Other platforms support

[zabojad]

Hi @Aurel300 !

Just a little discussion about this project to understand more where you are heading to.

Are you planning to support Android? (that would be awesome...).

[Aurel300]

Hey,

As the README says, other platforms are planned. The first target I will try after iOS will indeed be Android. I have installed the NDK, the emulator and the Android build tools on my computer, but I have no experience with how Android apps are actually bundled, so I will have to figure that out. I don't have an Android device, but it seems that hxcpp builds for Android only have one target, unlike iOS, which has a separate simulator and real device targets. So hopefully the apps will work the same on a real Android device as they do in the emulator.

Another platform in the list is OS X. This is a lower priority, because I want to get proper mobile apps first and foremost. However, OS X builds should be quite straightforward – I will need to use my extern generator to create externs from AppKit in the OS X SDK. The application bundling is slightly different than iOS bundling but not much.

After that perhaps Windows and Linux builds for various desktop environments? I have not decided yet. Did you have any suggestions?

[zabojad]

I'm mainly interested in the Android platform (along with the iOS one of course).

Unfortunately, I've not practice cpp development for too long so the only things I could give you a hand with are using, testing and reporting.

I do develop regularly for Android with the java SDK or with tools like Cordova (that I extend with plugins) so testing on different Android devices is not a problem (the Android simulator is crappy).

Well, I can only hope you'll get with a testable Android port soon!

[darmie]

Hi @Aurel300 do you mind if i take on the android bit?

[Aurel300]

@darmie Well, I don't have time for plumob in the coming week or two, so sure, why not!

See what you can do on your fork, try to make sure there are no additional Haxe dependencies for a simple build. The Android platform should use hxcpp's Android target, which uses Android NDK. The NDK and builds should absolutely work without Android studio (i.e. only the command-line tools are needed). I don't know how .apk's are packaged yet, but plumob should do that as well.

Good luck and thanks in advance.

[darmie]

Oh wow, hxcpp? I was hoping the build tool should work for Android Java as well. Considering Android UIs that doesn't need the NDK part. Why not have support for hxjava and hxcpp?

…

On Nov 28, 2017 20:25, "Aurel" ***@***.***> wrote: @darmie <https://github.com/darmie> Well, I don't have time for plumob in the coming week or two, so sure, why not! See what you can do on your fork, try to make sure there are no additional Haxe dependencies for a simple build. The Android platform should use hxcpp's Android target, which uses Android NDK. The NDK and builds should absolutely work without Android studio (i.e. only the command-line tools are needed). I don't know how .apk's are packaged yet, but plumob should do that as well. Good luck and thanks in advance. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAzwgiqX-XdS-ODSJZmZLzkH-wcFhBWKks5s7F41gaJpZM4QP6Ec> .

[darmie]

By simply having Android SDK and Android NDK stored somewhere on the computer, you don't need Android Studio. Everything can be built from the command line.

[Aurel300]

@darmie I'm somewhat biased against Java, and I'd think having both platforms use hxcpp would be simpler. Nonetheless, if you think building via the Java target would be easier to develop, go for it. As long as it brings us closer to native apps on the Android, it is a success.

[darmie]

Sure. Both will be fine. Because for non-gaming apps, I would rather use Java APIs directly to work with Android SDK, instead of writing JNI interfaces for them. I am working on a framework that would involve Java and iOS targets for Android and iPhone respectively, so instead of writing by own tool chain, I am thinking Plumob should suffice. By simply setting target flags like `android-native` for hxcpp Android Target and `android` simply for hxjava Android target. Kha has support for both Android native and Android Java, which I think is a good thing. I'll work on both and see who we can merge without breaking anything on iOS portion of the project. Cheers.

…

On Nov 29, 2017 13:46, "Aurel" ***@***.***> wrote: @darmie <https://github.com/darmie> I'm somewhat biased against Java, and I'd think having both platforms use hxcpp would be simpler. Nonetheless, if you think building via the Java target would be easier to develop, go for it. As long as it brings us closer to native apps on the Android, it is a success. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAzwgucbSJnVMWWE4vPUedNDQTLknetpks5s7VI-gaJpZM4QP6Ec> .

[Aurel300]

@darmie Any progress with the Android version? No pressure of course but please let me know if you can't make it for any reason so I know what's up.

[darmie]

@Aurel300 sorry for the long silence, life happened and day job stole my soul. I have not been able to do something tangible yet, although I did look into it.