File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
IDEs, Version Control and other tools
difference between android reference library and java build path dependency
Joined: Jan 03, 2004
Oct 04, 2012 13:30:09
Not sure if this is properly an Android question or an Eclipse question...
So I'm wrestling with trying to understand an inherited Android project in Eclipse. I'm an IntelliJ user, so be gentle.
In a project's Properties, I see two places where I can add libs that the project depends on:
1) Android --> Library. So the Library checkbox indicates that this project is/isn't a library. Then there's the list of projects that this project references as libraries.
Build Path --> Projects. Here I can add "Required projects on the build path".
So what's the difference between the two? My first guess it that #2 is just normal Java compilation classpath stuff and #1 is what to bundle up inside the .apk file. Am I close?
I agree. Here's the link:
subject: difference between android reference library and java build path dependency
What is difference between the User Libraries and external libraries
importing javax.servlet.* and javax.servlet.http using Eclipse in Ubuntu
Bean import/reference problem [1/2 solved]
Ill-advised or mistaken usage of a core class
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014