The idea would be to create a bind.json file that provides all required information to actually make and iOS/Android extension work with Haxe.
For instance, on iOS, it would allow to specify:
Objective-C/Swift files that are exposed to Haxe- A
podspec file (relies on Cocoapods) allowing to include and configure everything needed on iOS side of things
On Android, it would allow to specify similar informations:
Java files that are exposed to HaxeAndroid dependencies it may need (relies on Gradle dependency system, accepts jcenter libs)- An Android Studio project (or built AAR) dependency that will be included in final app
I would make it possible to run a single call of bind utility to make an iOS/Android extension work with various build systems.
It would be possible to generate a lime/openfl-compatible include.xml file if lime can handle bind requirements (Xcode workspaces with Cocoapods dependencies, Gradle AAR/jcenter dependencies).
The idea would be to create a
bind.jsonfile that provides all required information to actually make andiOS/Androidextension work withHaxe.For instance, on
iOS, it would allow to specify:Objective-C/Swiftfiles that are exposed toHaxepodspecfile (relies on Cocoapods) allowing to include and configure everything needed oniOSside of thingsOn
Android, it would allow to specify similar informations:Javafiles that are exposed toHaxeAndroiddependencies it may need (relies onGradledependency system, acceptsjcenterlibs)I would make it possible to run a single call of
bindutility to make aniOS/Androidextension work with various build systems.It would be possible to generate a
lime/openfl-compatibleinclude.xmlfile iflimecan handlebindrequirements (Xcode workspaces with Cocoapods dependencies, Gradle AAR/jcenter dependencies).