breautek commented on issue #1827:
URL: 
https://github.com/apache/cordova-android/issues/1827#issuecomment-3084194694

   It's not that simple unfortunately, I'm closing this as not feasible... I'll 
explain why. Cordova has never supported or exposed NDK builds, so Cordova 
doesn't even support a block to consume native C/C++ libs for android to 
compile. That means there is nothing for this preference to really target.
   
   It also means any plugin that did use NDK would have either:
   
   1. Prebuilt binaries completely outside of the Cordova environment and 
packaged them within a cordova plugin
   2. Extended gradle themselves to add NDK
   
   Both of which is not something Cordova can address. If the plugin authors 
shipped prebuilt binaries, they'll need to recompile them and update those 
prebuilt binaries. If they extended gradle using `<framework 
src="pluginGradle.gradle" custom="true" type="gradleReference" />` then they'll 
need to update their gradle NDK settings to build with NDK 28+ and to enable 
the build flag.
   
   Most plugins that I see that uses native libs ships the plugins with 
prebuilt binaries instead of compiling them at cordova build time. Or they 
simply reference an android library dependency that includes native libs which 
were not compiled for 16KB support.
   
   If we ever added support for NDK, so that android plugins can use C/C++ 
sources, we can also just simply enable 16KB page size support, as it's 
backwards compatible to 4kb devices. We don't need a flag for it. Supporting 
NDK can also be difficult if we intend to support C++, as there are several 
nuances around the std C++ lib.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to