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. Native platform filter for Android Market

When I try to upload my apk, i got this message "This apk requests 1
native platforms that will be used for Android Market filtering
Armeabi". Does
 this mean my app would not be visible to devices running on Armv7 or
x86? if yes, how can i remove this filter? because we created a share
library
 for armeabi and handles other devices in our code. Thus we would like
our app to be visible to all devices.
Thanks!

-- 

2. Trouble Adding Arc to Path

I am trying to add an arc to a path, but nthing gets drawn with each
call.  I have ensured that the passed RectF oval is dimensioned
properly, and calls to Path.addOval(oval, Path.Direction.CW) work
perfectly, but calls to either of Path.addArc(oval, 0, 180) and
Path.arcTo(oval, 0, 180) fail (nothing gets drawn).

Any suggestions on what I might be doing wrong?

Thanks!

-- 

3. getAssets(); crashing

4. Cannot install App on HTC Hero

5. Not able to install .APK file .

6. hey if you get the 32 bit errorhey if you get the 32 bit error

7. Keeping Synced App State