I'm guessing this is related here https://github.com/pfn/android-sdk-plugin/blob/master/src/tasks.scala#L947
On Wednesday, January 1, 2014 12:35:40 PM UTC-6, pfn wrote: > > same rules are applied regardless of build type > > > On Wed, Jan 1, 2014 at 10:23 AM, Daniel Skinner <[email protected]<javascript:> > > wrote: > >> I'm using the pfn/android-sdk-plugin and I don't think this is any fault >> of the plugin but i have an app that depends on >> https://code.google.com/p/aacdecoder-android/ which i already have >> compiled into a jar and dropped into libs. >> >> Debug builds work just fine but release builds cause the native lib to >> seg fault and having previously carried this over from a non-proguard >> project, I was thinking there are differing options set by the plugin based >> on build type (debug/release). >> >> I only noticed this single file in the repo for configuring proguard: >> https://github.com/pfn/android-sdk-plugin/blob/master/resources/android-proguard.config >> >> but might i be on the right track here? Or does the plugin apply the same >> rules regardless of build type? Digging into the source now >> >> -- >> You received this message because you are subscribed to the Google Groups >> "scala-on-android" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "scala-on-android" 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/groups/opt_out.
