Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
crash on run when "useProguard in Android := false" #114
andyli you may modify emulator if you wish. I run and debug my code with useProguard in Android := false. There are 2things that you need:
I must note that without it development process have a huge slowdown. Because I use AspectJ as AOP for alter scala code that add more compilation time than ever. Without "useProguard in Android := false" development is pain
If you have any questions PM me
Maybe I misunderstand something. I suspect, that @andyli discribe situation when installed application throw ClassNotFoundException or something like that (I saw it long time ago) because proguard skipped. There isn't scala runtime libraries at emulator by default and program crashed. It is default behavior. Just load all libraries to emulator. Or he point to other problem?
By the way, my copy paste incremental build process:
Generated 99 files
I think, that it is a very nice time for such amount of build work. Please, note size - only 823125 without proguard. All stable libraries already at emulator. I think this is what @andyli want - something like that
@ezh I think you understood @andyli correctly. If he's looking to get rid of some proguard time, there are at least two options: 1) use your predex/preload method, so proguard isn't needed at all; 2) use my patch, so that proguard isn't needed on the test project (but will still be needed on the main project). Yours is the better solution, but mine requires a little less work. I'm planning to try your branch myself soon.
@ezh I was simply using a unmodified emulatord the proguard skipped app crashed.
@loganj Thanks for your response, but I would like to skip proguard in the main project too.
Btw, it would be much nicer if there is a command in sbt that do all those predex/preload job.