3rd party jar

by Michael Lippautz » Tue, 10 Feb 2009 06:40:01 GMT


Sponsored Links
 Hi,

Having a problem here with including a 3rd party jar and couldn't find
any proper solutions on the group so far.

Compiling the HelloWorld app. with an additional 3rd party jar
(cglib-nodep). The jar is in the lib/ folder and has been added to build
path (add jar).

Compiling gives these warnings (about ~30 times):
warning: Ignoring InnerClasses attribute for an anonymous inner class
that doesn't come with an associated EnclosingMethod attribute. (This
class was probably produced by a broken compiler.)

I then tried to create the dex file myself (dx --dex --output=xx.dex
xx.jar) and succeeded without any errors. As far as I know an
incompatible jar file (incompatible byte code) shouldn't have passed
this one. Am I right here?

The problem is that by adding another 3 external jars the number of
warnings increases, compiling fills the buffer completely and finally
crashes the workspace.

Did I miss something?

I tried another approach by adding them as user lib but got an undefined
reference at runtime. (The .dex and .apk were far too small, so I think
they didn't get included)

Libs were:
cglib-nodep
commons-logging
antlr-runtime



--~--~---------~--~----~------------~-------~--~----~



3rd party jar

by Michael Lippautz » Tue, 10 Feb 2009 06:40:33 GMT


 Hi, (if you already received the message, sorry for that!)

Having a problem here with including a 3rd party jar and couldn't find
any proper solutions on the group so far.

Compiling the HelloWorld app. with an additional 3rd party jar
(cglib-nodep). The jar is in the lib/ folder and has been added to
build
path (add jar).

Compiling gives these warnings (about ~30 times):
warning: Ignoring InnerClasses attribute for an anonymous inner class
that doesn't come with an associated EnclosingMethod attribute. (This
class was probably produced by a broken compiler.)

I then tried to create the dex file myself (dx --dex --output=xx.dex
xx.jar) and succeeded without any errors. As far as I know an
incompatible jar file (incompatible byte code) shouldn't have passed
this one. Am I right here?

The problem is that by adding another 3 external jars the number of
warnings increases, compiling fills the buffer completely and finally
crashes the workspace.

Did I miss something?

I tried another approach by adding them as user lib but got an
undefined
reference at runtime. (The .dex and .apk were far too small, so I
think
they didn't get included)

Libs were:
cglib-nodep
commons-logging
antlr-runtime

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. xulrunner

Is it possible to install xulrunner application on android?

-- 

2. Calendar in Android 1.6 doesn't work

Hello,

I downloaded the source code of Android1.6 and try to compile. Then
the Calendar is displayed in the phone but I can not launch it.

Does anyone know why and how to fix?

Thanks in advance,

Nga

-- 

3. Rotated map view - how to get the touches back to where they belong?

4. Closing a particular tab in the Tabhost

5. Disabling browser intent

6. How to access the phone contacts in latest version of android 2.1

7. Pause Within a loop