On May 13, 5:01 pm, Mark Murphy <[email protected]> wrote:
> On Fri, May 13, 2011 at 5:31 PM, Spooky <[email protected]> wrote:

> > and
> > they are
> > the only two JAR files in the Yamba directory on the disk

I don't know why I wrote that...android.jar is referenced by the
.classpath file, but it is NOT in the Yamba path.  Oops.

> There should be no android.jar file in the Yamba directory on the
> disk, as that comes from your SDK installation, not the project.

Correcting what I wrote above:  jtwitter.jar is the only JAR file
in the Yamba directory.  android.jar is somewhere in the Android SDK
directory.

Wow...didn't think the power was going to come back this time....
Lots of thunderstorms moving through, power cutting out every
few minutes, so I'd better get  this posted while I can.

> I have never examined an Eclipse .classpath file to see what a proper
> one looks like with Android. Normally, when creating an Eclipse
> project, you never touch android.jar, as the Eclipse new-project
> wizard sets that up for you. All you do is copy your third-party JAR
> into libs/ and add it to your project with Add JAR on the Libraries
> tab of the Build Path dialog.

Hmmmm.....  It's not in the libs/ directory, and I don't recall how I
went about adding it (jtwitter.jar, that is---as you said, android.jar
was included automatically).  I'm going to back jtwitter.jar out, and
re-add it following the above bit by bit.  If another nearby lightning
strike doesn't stop me, I'll post a follow-up with the results.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to