Actually, i find this curious, if i call `android:package-debug` then a subsequent `android:install` produces this
> android:install [info] Collecting resources [info] Performing incremental resource merge [info] Generating R.java [info] [debug] cache hit, skipping proguard! [info] [debug] Forcing clean dex [info] Generating classes.dex [info] Packaged: wgts-debug-unaligned.apk (1.58MB) [info] Debug package does not need signing: wgts-debug-unaligned.apk [info] zipaligned: wgts-debug.apk [info] Installing... [info] [wgts-debug.apk] Install finished: 1.58MB in 7.39s. 219.64KB/s but a call to `android:package-release` followed by `android:install` produces this > android:install [info] Collecting resources [info] Performing incremental resource merge [info] Generating R.java [info] classes.proguard.jar is up-to-date [info] classes.dex is up-to-date [info] Signed: wgts-release-unaligned.apk [info] zipaligned: wgts-release.apk [info] Installing... [info] [wgts-release.apk] Install finished: 1.28MB in 5.65s. 232.67KB/s the debug is forcing a clean dex, so i tried `android:package-debug` to set debug (im new to this) then `clean`, then `android:install` to do the debug build and install all in one go. And I get the same error as the release version. So whatever is happening during this big of the logging [info] [debug] cache hit, skipping proguard! [info] [debug] Forcing clean dex [info] Generating classes.dex is producing a proper build. So to reiterate, i have to call `clean` `android:package-debug` `android:install` for a proper build. Anything else is causing a segfault for me. On Wednesday, January 1, 2014 12:23:35 PM UTC-6, Daniel Skinner 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]. For more options, visit https://groups.google.com/groups/opt_out.
