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. Operation not permitted

Hi,

Why do I get this ? I have a set of Vendor Specific commands that hciattach
would send over the hci0 socket interface, I get these when I try and send
them,

I//system/bin/hciattach(  959): Cannot send hci command to socket: Operation
not permitted
I//system/bin/hciattach(  959): Can't initialize device: Operation not
permitted

It had eventually came down to function writev in hci_send_cmd, and the
writev in itself is failing.

I am starting hciattach & hcid from UI, so the user/owner is 'bluetooth'
although I do get the same message when I try and run as 'root.
Here's the ocf/ogf when I get that error,

I//system/bin/hciattach(  959): hci_send_cmd:writing 63, 268
I//system/bin/hciattach(  959): hci_send_cmd: errno: 1


Any ideas ??

regards,
Pavan

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. Can we charge some externals stuffs for a paid Android Market game

Here the answers at this topic :
http://groups.google.fr/group/android-discuss/browse_thread/thread/f7b87462549b3a3d?hl=fr
--~--~---------~--~----~------------~-------~--~----~

3. How can i check the mode of orientation?

4. How to setup the DNS to access the external nework

5. Bundles and serializable objects - what is actually stored?

6. How to setup the DNS to access the external nework

7. Localizing layouts?