For me, and I assume lots of other developers, I need to find a way to do this without disrupting a large population of Eclipse ADT users. So.... moving files to non-traditional locations is not an option.
-Paul On Friday, May 23, 2014 2:27:52 AM UTC-4, Alexander Zhigulich wrote: > > Amazing! Thanks a lot. > > On Wednesday, June 5, 2013 9:11:30 AM UTC+3, Yonnie Lu wrote: >> >> There is a topic we known as: "https://gist.github.com/khernyo/4226923";, >> But i have try this method in gradle plugin 0.4.0+, it doesn't copy the so >> libs to apk. >> So I'm confused. But I figured out a new way to hack this before gradle >> support. >> The way is: use jar to copy so libs. Is it amazing?right?. Let me show >> how-to: >> If you have the following structure: >> project >> |---libs >> |---armeabi/xxx.so >> |---xxx.jar >> |---xxx.jar >> 1.We archive the armeabi folder to zip named:armeabi.zip with the folder >> in zip like: lib/armeabi/xxx.so >> 2.Rename armeabi.zip to armeabi.jar and put armeabi.jar into libs folder >> with the other jars. >> 3.And when we call >> dependencies { >> compile fileTree(dir: 'libs', include: '*.jar') >> } >> in our build.gradle file, it will extract the so libs to the apks. >> >> As we know, only class files will be packed into classes.dex file and >> other files will be extracted to the apk as the structure in the jars. >> So, That's how-to hack. Easy and amazing. Cool,right? >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
