Native Extensions: 64/32-bit Android resource copying

How does the res dir work for ARM64 android in native extensions? I have the following file structure and if I make a 32+64bit build, only the files in fmod/res/armv7-android end up in the final APK. The 64-bit libraries are not copied.

Even if I do only a 64-bit build, the files in armv7-android are still copied. It looks like there’s no per-architecture distinction when it comes to copying resources in res, which is weird because there is a distinction for libraries in fmod/lib/arm64-android and fmod/lib/armv7-android.

1 Like

I think it’s due to the new feature that it’s not supported (yet).

I’m working in that particular piece of code right and I’ll try to see if I can fix that too (in time for the release on monday). No promises on that though (short on time today), so probably in the next release.

The obvious workaround is ofc to put all the resources under armv7-android/lib/* folder until I’ve fixed that issue.

That said, the proper solution in this case is ofc for the libraries to be residing in the actual /libfolder (as opposed to under the /resfolder), and let the build+bundle step handle it.

4 Likes