You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in version: HG 2.0 Reported for operating system, platform: Android (All), All
Comments on the original bug report:
On 2015-12-03 17:43:44 +0000, Martin Gerhardy wrote:
Currently it is not possible to upgrade to the latest SDK and compile SDL with it, because they removed the ant support and only maintain gradle. Are there plans to add support for this? If so, what are they? Remove ant completely and only support the gradle stuff?
On 2016-06-30 07:20:20 +0000, Sylvain wrote:
Hello, Just writing that I am building with gradle (without eclipse, nor android studio) under linux.
At first it seems a little bit painful to set-up, but afterwards, it seems faster and more reliable.
Let me know if you want me to share some information.
On 2016-10-01 20:19:20 +0000, Sam Lantinga wrote:
Yes, I think the right approach is to remove ant support and only support gradle.
Sylvain, can you provide information on how to do that?
Thanks!
On 2016-10-01 21:08:26 +0000, Sylvain wrote:
Created attachment 2567
build.gradle template
Here's some explanation:
Android NDK is still needed (preferably with env variable: $ANDROID_NDK_HOME)
attached file "build.gradle" is needed.
"gradle" from: http://services.gradle.org/distributions/ is needed
Download the "bin" archive, version 2.14.1
You may need to regenerate it, doing: ~/Downloads/gradle/gradle-2.14.1/bin/gradle wrapper
Copy the files into your application directory to have the following structure:
AndroidManifest.xml
...
gradle/
gradle/wrapper
gradle/wrapper/gradle-wrapper.jar
gradle/wrapper/gradle-wrapper.properties
gradlew
build.gradle
(maybe also "gradlew.cmd" for windows).
(and "proguard.pro" if needed ..)
Those files are not needed anymore:
ant.properties
build.xml
build.properties?
Usage:
build with:
./gradlew assembleRelease
build, sign, install on device with:
./gradlew appStart
User needs to customize "build.gradle":
change its "applicationId"
set all the versions correctly to fit its android build system ("buildToolsVersion", "dependencies", SDK).
fill the signing configuration
On 2017-08-24 15:05:52 +0000, wrote:
A couple of things to consider:
First, as of Android gradle plugin v.2.3.3, NDK builds are supported natively, so there's no need to execute ndk-build by hand. Instead, you would have something like this in your build.gradle file:
This also has an added benefit of integrating nicely with Android Studio, allowing to use its C/C++ editor and debugger.
Second, cmake seems to be the preferred way to add native code to an Android project right now. Official Google tutorials show how to use cmake, and creating a new project with C++ support will create a cmake-based project. Gradle seems to not run its ndk-build jobs in parallel, resulting in really long build times, while cmake projects are using all CPU cores during build.
On 2017-08-24 18:24:56 +0000, wrote:
Messed up my example... Should have been something like that:
/.../
android {
externalNativeBuild {
ndk-build {
/* Specify path to your Android.mk file */
path "path/to/android.mk"
}
defaultConfig {
externalNativeBuild {
ndk-build {
/* Arguments for ndk-build */
arguments "NDK_APPLICATION_MK:=Application.mk"
/* You can specify your cFlags, cppFlags, abiFilters and targets here as well */
}
}
/* Other defaultConfig paramters go here */
}
/* You can specify additional ndk-build parameters per build type */
buildTypes {
release {
externalNativeBuild {
ndk-build {
cFlags "-DRELEASE_BUILD"
}
}
}
}
/* other stuff */
}
Syntax for CMake doesn't differ at all, you just replace "ndk-build" with "cmake".
Thanks for the news, the android gradle plugin has improved in the meantimes!
I just tried it and here's my build.grade file updated.
Some remarks:
it's not "ndk-build" but "ndkBuild"
you can have parallel builds with: arguments "-j10"
I was forced to set the abiFilters to what I wanted. It wouldn't use the one from Android.mk. (though, all other variables from Android.mk are used!)
I haven't tried CMake with Android. I don't really see the point of it. You still need a cross-compiler, so eventually the Android NDK.
On 2017-08-26 18:11:04 +0000, wrote:
(In reply to Sylvain from comment # 6)
Created attachment 2893 [details]
build.gradle template
Thanks for the news, the android gradle plugin has improved in the
meantimes!
I just tried it and here's my build.grade file updated.
Some remarks:
it's not "ndk-build" but "ndkBuild"
you can have parallel builds with: arguments "-j10"
I was forced to set the abiFilters to what I wanted. It wouldn't use the
one from Android.mk. (though, all other variables from Android.mk are used!)
I haven't tried CMake with Android. I don't really see the point of it. You
still need a cross-compiler, so eventually the Android NDK.
Thanks for mentioning those points! I should've double-checked the ndkBuild stuff. Yeah, you have to use abiFilters to specify your targets now, but I guess that makes adding platform-specific condidionals to build scripts simplier? If I understand correctly, now ndk-build or cmake will be running for each abi separately.
Well, one of the reasons SDL might want to use CMake to build for Android is that SDL would no longer need Android-specific .mk files, so that's one less build system to worry about :-) Seriously, though, CMake is much more flexible than Android's custom makefiles. And in my opinion it's more transparent (and maybe even easier to understand) than those .mk files - at the very least, CMake is better-documented than the old Android build system, and there's always a CMakeCache that I can look through to get a sense of what's happening.
Sure, you'll need NDK eventually, but CMake for Android does not create makefiles, it targets (and runs) ninja build system. So only the toolchain+sysroot part of the NDK gets used.
As an added bonus, you can create apps that are easily buildable (without external scripts, with a single set of build scripts) for multiple platforms. Here's an example I've made: https://github.com/sfalexrog/Imgui_Android
There are, unfortunately, some caveats when using CMake for Android. You want to use Google's version of CMake that can be downloaded with sdk tools, because it has some "gradle integration" that a usual CMake doesn't have. That might not sound so bad, but the binary they provide links to a particular version of OpenSSL that's not in Fedora repositories, so I had to build one myself. It also expects to find OpenSSL library in /usr/lib, so I couldn't just place the file near the executable, and had to put it among other system libraries. It's like Google means "for Ubuntu" when labeling their tools as "for Linux".
On 2017-08-30 20:02:25 +0000, Sylvain wrote:
Created attachment 2903
patch
This is a patch to build with gradle using the script androidbuild.sh
It drops "ant" build stuff.
you need to have env ANDROID_HOME set to you SDK location and gradle in path.
I have updated the sdk version to 16 because SDLActivity code needs it, but according to the documentation we should updated it to latest.
Though the minSdkVersion remains 10.
On 2017-08-30 20:14:25 +0000, Ryan C. Gordon wrote:
I've been asked about this a lot recently; Sam, should we cram this into 2.0.6, or is it too risky?
--ryan.
On 2017-08-30 20:24:39 +0000, Sylvain wrote:
BTW, I haven't tested androidbuild.sh on window nor macosx. only on linux.
On 2017-08-30 21:27:06 +0000, Sam Lantinga wrote:
It's too risky for 2.0.6, but I'm getting it in right after we release.
On 2017-09-12 16:22:03 +0000, Sylvain wrote:
Also a patch there : bug 3510
On 2017-10-23 22:27:00 +0000, Sam Lantinga wrote:
*** Bug 3510 has been marked as a duplicate of this bug. ***
I believe you don't have to check in *.iml files - they are generated by the IDE and will be overwritten anyway.
AndroidMatifest.xml might be simplified as well, if I'm not mistaken. The uses-sdk property is overriden by gradle anyway (and isn't minSdkVersion 14 or 16 nowadays?)
I'm not sold on disabling automatic ndk-build in build.gradle - wasn't having a "single-click build" from Android Studio one of the points for this change? And I'm not sure if C/C++ syntax highlighting, autocompletion, and native debugging are going to work with this setup. Then again, I'm not sure what's the proper process of using SDL2 in an Android app is, so far I've been simply building it alongside the app (possibly rebuilding the whole library), so maybe I've been doing it wrong all along.
Still, really happy to see that! Will try to send something more meaningful (i.e. patches :-) ) soon!
Updated Android build tools version, which bumped minimum deployment target to API 14
Also added native code to the Android gradle project, which allows using gradle or Android Studio to build the entire SDL application without a separate ndk-build step.
This is really quite elegant. :)
Thanks!
On 2017-10-24 06:42:17 +0000, Sam Lantinga wrote:
sfalexrog, I don't really speak CMake, but the benefits of tracking Google's recommneded development path and parallel make seem worth it, so feel free to enter a separate bug to track adding Android CMake support.
Thanks!
On 2017-10-24 09:10:16 +0000, wrote:
Created attachment 3037
Remove redundant lines from AndroidMatifest.xml
These fields are redundant now that SDL uses Gradle for Android builds - they are set from build.gradle
On 2017-10-24 09:37:22 +0000, Sylvain wrote:
I was about to write the same patch.
Indeed, we don't need to write Sdk version in AndroidManifest.xml, it's overwritten into a temporary file: "build/intermediates/manifests/full/release/AndroidManifest.xml"
(Maybe also APP_PLATFORM can be remove from Android.mk, since it's on the command line)
NDK-r15 has bumped the min sdk version to 14, but SDL2 still works fine with min sdk 10.
I personally still see downloads (~100 per day) for user with android 2.3 - 2.3.7. (less with android 3.x), and I will keep my minSdkVersion to 10.
But I understand that for new user that just setup android studio, use latest ndk and SDL2. They can face this issue and be disappointed.
I don't mean the patch below to be applied, but if you keep the minSdkVersion to API 14, please don't remove the java code that run belows API_14.
Thanks
Also, some reading, they suggest to use the max compileSdkVersion:
Be aware, though, that if you're using a high enough targetSdkVersion, you might run into stuff like missing runtime permissions (for filesystem access, for example). It's fine if you're shipping your assets with your game (you can simply extract those to an app-local folder, which is always accessible, though you'll make users with tiny internal storage and SD cards sad), but if you're accessing any outside locations, you'll have to request these permissions at runtime if the device is recent enough.
And I'm not sure if that's still configurable, but you should probably compile your native code with a lower API version, since you might end up linking against libraries that don't exist in an older device (breaking changes in bionic, like missing rand(), come to mind)
Java code still works fine with API 10. But some function are disabled:
no clipboard notification (need API 11)
no motion event (need API 12)
only 1 mouse button (API 14)
no joysticks (API 14/16),
maybe other stuff. (some flags like KeyEvent.KEYCODE_ZOOM_INdoes not exist).
indeed, at targetSdkVersion 23, you need to request permissions at runtime.
but SDL only needs normal permissions, that are granted at installation. https://developer.android.com/guide/topics/permissions/normal-permissions.html
like INTERNET / VIBRATE / ACCESS_NETWORK_STATE
WRITE_EXTERNAL_STORAGE seems not to be in the list, but it says "Starting in API level 19, this permission is not required to read/write files in your application-specific directories returned by getExternalFilesDir(String) and getExternalCacheDir()."
RECORD_AUDIO, which is commented out, probably needs to be granted.
to avoid API breaking changes like rand(), atof(), and so on. Yes, there is a nasty issue there.
one needs to make sure set minSdkVersion to the same as APP_PLATEFORM.
The text was updated successfully, but these errors were encountered:
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
build.gradle template (build.gradle, text/x-csrc, 2016-10-01 21:08:26 +0000, 3394 bytes)build.gradle template (build.gradle, text/x-csrc, 2017-08-25 13:21:14 +0000, 2440 bytes)Reported in version: HG 2.0
Reported for operating system, platform: Android (All), All
Comments on the original bug report:
On 2015-12-03 17:43:44 +0000, Martin Gerhardy wrote:
On 2016-06-30 07:20:20 +0000, Sylvain wrote:
On 2016-10-01 20:19:20 +0000, Sam Lantinga wrote:
On 2016-10-01 21:08:26 +0000, Sylvain wrote:
On 2017-08-24 15:05:52 +0000, wrote:
On 2017-08-24 18:24:56 +0000, wrote:
On 2017-08-25 13:21:14 +0000, Sylvain wrote:
On 2017-08-26 18:11:04 +0000, wrote:
On 2017-08-30 20:02:25 +0000, Sylvain wrote:
On 2017-08-30 20:14:25 +0000, Ryan C. Gordon wrote:
On 2017-08-30 20:24:39 +0000, Sylvain wrote:
On 2017-08-30 21:27:06 +0000, Sam Lantinga wrote:
On 2017-09-12 16:22:03 +0000, Sylvain wrote:
On 2017-10-23 22:27:00 +0000, Sam Lantinga wrote:
On 2017-10-23 22:27:49 +0000, Sam Lantinga wrote:
On 2017-10-24 04:35:08 +0000, wrote:
On 2017-10-24 06:37:16 +0000, Sam Lantinga wrote:
On 2017-10-24 06:42:17 +0000, Sam Lantinga wrote:
On 2017-10-24 09:10:16 +0000, wrote:
On 2017-10-24 09:37:22 +0000, Sylvain wrote:
On 2017-10-24 10:12:40 +0000, wrote:
On 2017-10-24 10:46:30 +0000, wrote:
On 2017-10-24 12:55:23 +0000, wrote:
On 2017-10-24 18:12:18 +0000, Sylvain wrote:
The text was updated successfully, but these errors were encountered: