This is the mail archive of the kawa@sourceware.org mailing list for the Kawa project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: More Android shrinking/proguard trouble


I've now got it narrowed down to the following differences in contents of the jarfiles:

--- /tmp/lap.jar	2012-07-04 16:58:46.655131809 +0200
+++ /tmp/desk.jar	2012-07-04 16:51:00.015132187 +0200
@@ -281,8 +281,6 @@
 gnu/kawa/servlet/HttpOutputStream.class
 gnu/kawa/servlet/HttpRequestContext.class
 gnu/kawa/servlet/KawaAutoHandler.class
-gnu/kawa/servlet/KawaHttpHandler.class
-gnu/kawa/servlet/KawaHttpHandler$Context.class
 gnu/kawa/servlet/ServletPrinter.class
 gnu/kawa/slib/condition.class
 gnu/kawa/slib/condition$Mntype.class
@@ -593,6 +591,7 @@
 gnu/kawa/util/HashNode.class
 gnu/kawa/util/IdentityHashTable.class
 gnu/kawa/util/IntHashTable.class
+gnu/kawa/util/PreProcess.class
 gnu/kawa/util/RangeTable.class
 gnu/kawa/util/RunTestScript.class
 gnu/kawa/util/WeakHashNode.class

lap.jar is the one the fails with proguard, while desk.jar works fine.

Considering the configure command line (and Makefile!) is identical on both systems, I have no idea why those extra classes gets pulled into the jar on my laptop.

Thanks,

Marius K.

On Wednesday 04 July 2012 04:38 PM, Marius Kjeldahl wrote:
Following up on my own post;

It's related to different versions of the kawa.jar file. If I copy the
jar over from the system where compilation works, compilation works fine
on the other system as well.

As for figuring out why kawa.jar is different on the two systems, I have
no idea. They both run the same distribution version of linux (although
with different kernels), they have the same version and release of java
installed. The kawa configure script generates identical Makefiles on
both systems. And comparing config.log from the two systems only show
differences in uname (linux 3.5 on one and 3.2 on the other, the latter
is the one that generates kawa.jar files that make proguard fail). Yeah,
and finally, compiling my test program in debug mode (running the make
script with "./make debug") works fine on both systems.

I'll keep digging and try to figure out why kawa.jar are different on
the two systems, despite identical configuration, but any ideas are
welcome.

Thanks,

Marius K.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]