Conversation

Replying to

and

@erincandescent

Do you know what compileSdkVersion means in practice? If that determines the java toolchain you get when building with gradle-controlling-CMake, but I am getting the minSdkVersion java toolchain when using Cmake directly, that might explain the discrepancy

1

Replying to

and

@erincandescent

compileSdkVersion is the toolchain version and you're meant to always use the latest one. You should be ending up building everything (Java and native) with latest toolchain but with minSdkVersion set appropriately (__ANDROID_API__ for native) so it's backwards compatible.

1

Replying to

and

@erincandescent

No matter how old the API version that you support, you're meant to be using compileSdkVersion 30 and targetSdkVersion 30 (but in practice, targetSdkVersion 29 is normal right now, and it'll be almost a year before Play Store enforces 30).

1

Replying to

and

@erincandescent

compileSdkVersion 30 should pretty much just work. targetSdkVersion 30 requires supporting the latest restrictions, changes, etc. for newer API levels while still having code to support the older API levels you support so that actually involves work and runtime code decisions.

1

Replying to

and

@erincandescent

I believe the idea is Oculus has never shipped an Android OS newer than 8. (Still confused if I can use AAudio or not!)

1

Replying to

and

@erincandescent

You should probably still use compileSdkVersion 30 to have newer tools with a bunch of bug fixes and improvements but might as well leave targetSdkVersion at 26 if they don't make you deal with the newer restrictions and wouldn't be able to properly test higher than 26 anyway.

1

Replying to

and

@erincandescent

Is it surprising to you I am hitting the chk issue at CMake-minSdkVersion 23, given I now know (because I get the duplicate symbol error) that __ANDROID_API__ is being set properly to the minSdkVersion?

1

Replying to

and

@erincandescent

You could add something like this to the code: #if __ANDROID_API__ != 21 #error "wrong minSdkVersion" #endif

1

Replying to

and

@erincandescent

Well, effectively I know this is happening because I set __ANDROID_SDK__=21 manually and it said nuh uh, __ANDROID_SDK__ is already 26

1

Replying to

and

@erincandescent

It should be fine if it's actually set to the same value that you end up having for minSdkVersion at runtime. If it's 26 for the native code and 23 at runtime, it'll break. If you set minSdkVersion to 26 so it matched it wouldn't break, since it'd match what it's using to build.

1

Replying to

and

@erincandescent

Still must have a mismatch between build time __ANDROID_API__ and runtime minSdkVersion if you're getting the sendto error.

7:43 PM · Mar 16, 2021Twitter Web App

Replying to

and

@erincandescent

Tried #if __ANDROID_API__ == 23 #error "API level is correct-filesystem" #endif in both a source file in the "good" lib and the "bad" lib. Errored both times. Could a mismatch between debug-config and release-config be the problem? Trying that next.

1

Replying to

and

@erincandescent

wait, what does "runtime minSdkVersion" mean exactly?

1

Show replies