Cross platform has been well studied on desktop, but this is an exploration in doing that on mobile and an open request for comments and improvements.
"mobile times 3", Android, iOS, and Windows Phone. (todo, windows phone support)
python(required for gyp)- xcode &
xcodebuild - android ndk and
ndk-buildon your PATH to build for android - windows phone developer tools (eventually...)
- Run
git submodule initandgit submodule updateto download json11. - Run
make play. You should see "Hello, #{your login name}" printed to the console, if so, you seem to already have all the requirements met for building.
Run make play ios or make play mac
Running any of the make commands will automatically download gyp and create
.xcodeproj files for each platform.
Build files are generated in build_ios/mx3.xcodeproj, build_mac/mx3.xcodeproj, and GypAndroid.mk but be careful,
running make commands again will overwrite any changes you make to these files. If you need to change something,
you should be able to do so from common.gypi or mx3.gyp and recompile your buildfiles.
Make targets:
clean- clean all generated filesmake test- run the c++ testsios,android,mac- builds a static library for each platformmake play- to write some quick "playground" style code in objc (see objc/play.m)
- mx3.gyp - gyp meta-build file for per-target settings
- common.gypi - a gyp include which defines project wide settings
- Application.mk - the android make file
- Makefile - helper for interacting with gyp, and using command line builds (no xcode!!)
- deps/ - third party dependencies
- example_mac/ - a external xcodeproj which uses libmx3 ("the client" in a client/server model)
- include/ - header include paths, no code here
- objc/ - objc bindings to mx3::Api. Very simple api translation (NSString * -> std::string, lowerCamel -> under_lower, etc.)
- src/ - the c++ library, there should be no objc/java code here ("the server" in a client/server model)
- test/ - c++ tests