But since Google deprecated the adb CLI (because they did, right?) I’m stuck on XCode for now. But if I could get a nice debugging workflow going through Emacs and Gradle alone, I’d love that. So I use XCode, as I use that for my main employment anyway. The problem is that developing in Emacs on OSX is a pain because I’d have to adjust all my hotkeys and bindings I already learned, which by now is in my bone marrow as one says in Sweden haha. I just prefer Emacs whenever I can stick to it. While I do know the struggle of Android Studio (Or any IDE from Jetbrains because they all use the slow a** JVM), It’s not to bad if you have a Good system This means that if I’m using my Google Pixel 2 to debug, It will only build arm64-v8a and not armeabi-v7a | x86 along with it. The main reason to use Android Studio is to debug on Android Devices and It’s the most cross platform IDE among Mac, Linux, and Windows & depending on if your trying to support multiple abi’s or not, Android Studio 3.0 will build in context of the device. True, It’s using gradle so you technically don’t need Android Studio, But you’ll probably need to install it anyways to get all build tools easily at least.
And it’s this stage that might become infeasible. I’m going to use fastlane to build, package and deploy whenever a git tag is deployed, but I’d still want to build the latest master branch and run tests, whenever possible. I did Google and search for a solution but didn’t find one, but I did find that other people also have the same experience when it comes to the Android NDK. If I configure TravisCI to keep a cache I might run into other issues too. Doing the same on Android takes much, much longer (10m 20s last night, for just one ABI), and won’t be feasible for testing or building unless I explicitly only build Android on releases. Me cleaning the project in XCode, which means recompling Cocos2D-x and my own code, still lands at around ~2 minutes.
Ussualy it takes time to first time compile android, if u keeping source code of project in same place and not changing android.mk application.mk and not changing branches then second compile should be much faster on android, same goes to ios
0 kommentar(er)
