I wholeheartedly agree with Guillaume that Android lib projects would
be a good feature. But maybe the case I have in mind requires
something different.
I have ported to Android an LGPL library, libdmtx. This library has
native code and JNI wrapper. I created an org.libdmtx APK which
installs the
The problem here is that the ADT plugin tries to upload the referenced
android projects in build path as separate APKs instead of mixing the code
like in previous SDK releases.
Even if several APKs are uploaded, there is no link between them on the
device and so the VerifyError occurs when
Eric Chen, what is that build.xml file ? And what exaclty did you modify in
the .classpath and the manifest files ?
Handtwerk, I don't know if the problem also affects the Ant tool chain or
just the Eclipse one, someone should test that.
(When I say switching to J2SE projects, it only affects the
I've got a working solution to this similar to your hint about J2SE
projects. Assuming your lib project is an android project, modify
the .project file to remove all Android builders and Android natures.
I removed the resourcemanagerbuilder, precompilerbuilder,
apkbuilder, and androidnature. My
This sounds like a great workaround, so I'll try that next week.
Thanks for the tip.
2009/4/30 JMoger james.mo...@gmail.com
I've got a working solution to this similar to your hint about J2SE
projects. Assuming your lib project is an android project, modify
the .project file to remove all
Hello,
Editing the .classpath is a good solution. Let me explain why.
ADT supports referenced projects so that you can have library projects
reused by your main Application project.
In the past, the build system provided by ADT just looked at the list
of referenced projects, and added their
Android lib projects would be a good feature.
But why not having a dependency system between APKs like debian packages ?
2009/5/1 Xavier Ducrohet x...@android.com
Hello,
Editing the .classpath is a good solution. Let me explain why.
ADT supports referenced projects so that you can have
Well, I met the same issue.
Does anyone have any idea about this?
Best regards,
On Tue, Apr 28, 2009 at 11:14 PM, Guillaume Perrot
guillaume.p...@gmail.com wrote:
We have an application cut into 3 android projects:
* Project REAL (the real android project)
* Project LIB1 (an android project
Hi Guys,
We've had the same problem with ProSyst mBS running on cupcake. After
some checks we found that it depends what JDK you use for building your
jar files before DEXing them. In general here is the info:
We've checked with the following JDK versions: jdk1.5.0_06, jdk1.5.0_10,
I use a temporary solution thanks to a comment of Raphael on the
original topic (I posted twice, sorry):
* LIB1 and LIB2 are now java projects
* I removed the sun JRE from build path
* I added android.jar instead, for SVN convenience, I added thanks to
an Eclipse PATH variable (pointing on the
I fixed the problem just by modifying .classpath, AndroidManifest.xml and
adding build.xml
Best Regards
Eric Chen
On Wed, Apr 29, 2009 at 7:52 PM, Guillaume Perrot
guillaume.p...@gmail.comwrote:
I use a temporary solution thanks to a comment of Raphael on the
original topic (I posted
I did not understand your solution Eric Chen, could you explain exactly what
you modified ?
2009/4/29 Eric Chen jude...@gmail.com
I fixed the problem just by modifying .classpath, AndroidManifest.xml and
adding build.xml
Best Regards
Eric Chen
On Wed, Apr 29, 2009 at 7:52 PM, Guillaume
We've had the same problem with ProSyst mBS running on cupcake. After
some checks we found that it depends what JDK you use for building your
jar files before DEXing them. In general here is the info:
We've checked with the following JDK versions: jdk1.5.0_06, jdk1.5.0_10,
jdk1.5.0_12,
The JDK is clearly not the problem here, I don't know what he's talking
about as there are several causes that can trigger a VerifyError but in this
discussion we deal with the latest ADT Eclipse plugin release.
The problem here is that the ADT plugin tries to upload the referenced
android
Ok , my way diff the project new with old sdk ,there are 3 modified files
.classpath, AndroidManifest.xml and adding build.xml. It will work
Best Regards
Eric Chen
On Thu, Apr 30, 2009 at 2:40 AM, Guillaume Perrot
guillaume.p...@gmail.comwrote:
The JDK is clearly not the problem here, I don't
15 matches
Mail list logo
