How to build CM system app without odex?

Question

When I build CM7 's system app (eg. ADWLauncher) , I switch to ADWLauncher's folder and run "mm" command, then I get .apk and .odex file, How can I just get .apk file with dex in it. I mean should I change somewhere in Android.mk or generic.mk to let the compilation just result apk file which can instsall directly.

I'd like to know the answer too... – thom_nic Jun 15 '12 at 00:07 — thom_nic, Jun 15 '12 at 00:07

score 3 · Answer 1 · answered Mar 01 '16 at 07:55

3

Try this mm WITH_DEXPREOPT=false -B

answered Mar 01 '16 at 07:55

siva

1,850
13
14

score 1 · Answer 2 · answered Sep 03 '13 at 11:48

1

You can use backsmali which can combine odex and apk files

baksmali -a [api_level] -x [odex_file] -d [framework_dir]

Or change the WITH_DEXPREOPT environment variable in

build/target/board/generic/BoardConfig.mk

answered Sep 03 '13 at 11:48

sherif

2,282
19
21

George Hilliard · Answer 3 · 2015-01-20T15:06:53.793

This usually happens (at least to me) when I have not declared a device I'm building for with breakfast. For example, without running breakfast hammerhead, I got Dialer.apk and arm/Dialer.odex in the output directory. Furthermore, the device refused to run the binary, even after putting the .odex file in place.

Running breakfast first causes make to generate a single proper Dialer.apk that installs cleanly (using adb root/remount/push) on my device.

How to build CM system app without odex?

3 Answers3