Which is different to what Gradle uses by default:
ANDROID STUDIO C ANDROID
Targets is mentioned here Guide - Link Gradle to your native library - Specify optional configurations.After Android Studio sync my gradle project, I see the following message in the event log:Īndroid Studio is using this JDK location: apply plugin: ''ĬonsumerProguardFiles 'proguard-rules.pro' I've checked breakpoints in a library work in Android Studio 3.2.1. Here's a copy from my project as a sample, partially modified from original one but may work. Setting CMake version to 3.10.x (3.10.2 for me) also seems buggy. Wrong file contents are shown in editor and build fails, sometimes. As far as I've experienced, Android Studio 3.3, gradle:3.3.0, gradle-4.10.1-all have severe bug in VCS(git).
ANDROID STUDIO C FOR ANDROID
I know there are newer versions for Android Studio, Gradle and CMake but they are buggy, so I chose current environment.
ANDROID STUDIO C CODE
externalNativeBuild tree properly even if clean or rebuild is called, and confuses native code build configs.
NB.3 Seems version dependent but Gradle in Android Studio does not clean. No need to set it for debug build, as debuggable flag is set as default. NB.2 debuggable true is for release build to enable debugging. If it seems to work without any targets, check files on device. The built output is in (project)/app/build/intermediates/cmake/(flavor)/obj/(cpu architecture). NB.1 If targets is omitted, Android Studio seems to build no targets. To synchronize, select /data or /data/app and choose Synchronize. NB: Synchronize menu of device file explorer does not synchronize properly under lib or (cpu arch.) directory. Files are in /data/app/(package name)/lib/(cpu arch.)/. They are overwritten basically, but clear them manually depending on needs. so files in intermediate directory, but it's optional.Īndroid Studio does not clean libraries in the test device. I also delete build folder, as it contains. Open project directory in explorer and delete build cache (.externalNativeBuild folder) manually and build the project again. If breakpoints doesn't work after build, old garbage may be left in the build cache and causes problems. Mylibrary apply plugin: ''ĬppFlags "-fexceptions", "-std=c++11", "-DJSONCPP_NO_LOCALE_SUPPORT"įirst, check debug variant is selected for library.Īs your adle has a setting, path "src/main/cpp/CMakeLists.txt", it won't build I think. Implementation ':constraint-layout:1.1.3'ĪndroidTestImplementation ':runner:1.0.2'ĪndroidTestImplementation '.espresso:espresso-core:3.0.2' Implementation fileTree(dir: 'libs', include: ) Implementation project(path: ':mylibrary') ProguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro' TestInstrumentationRunner ".AndroidJUnitRunner" But it is not working since Android Studio upgrade.Īpp apply plugin: ''ĪpplicationId "" There was enough for native debugging earlier. I've added defaultPublishConfig "debug" into mylibrary adle and debuggable true to app adle. Now I'm unable to stop on breakpoints in native code, native debugger became active only after a SEGFAULT crash.
I've created a demo Android project with native support, added a library to it and moved all native code into the library. I've tried all the ways found on StackOverflow and still facing the issue.
0 kommentar(er)
