I built my own game engine from the ground up for this project and the hardest problem I have had to solve this entire project remains "how do you build anything at all for Android"
4
13
209
Conversation
It's occasionally just really shocking that Google still hasn't faced just how bad the developer experience targeting the NDK is. Apple is actively hostile to third party devs yet they were not able to create something as hostile as the Android build system(s) became by accident
6
16
119
Replying to
I think they just don't want the NDK to exist if possible, code with pointers isn't for you to write.
1
Replying to
This to me says "they don't want cross platform software" and who on earth is going to write Android-exclusive software
1
3
Also as an interesting piece of trivia, I am actually targeting a non-phone hardware platform which chose to use Android as its base but which does not run conventional Android apps and does not, in fact, appear to support Java at all
But still uses the Android/Java build system
1
9
The funny part about it is that Android SDK/NDK build system isn't what's used by Android itself. Android itself is busy replacing a far superior build system to the one they make app developers use with a better one, after previously going through a past replacement like that.
2
1
It's really hard for me to understand why they decided to use gradle, etc. for the SDK. They would never use that nonsense internally. There's no way Google engineers would put up with it. Android doesn't use that itself and they definitely don't use it for Google apps either.