File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes IDEs, Version Control and other tools and the fly likes difference between android reference library and java build path dependency Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "difference between android reference library and java build path dependency" Watch "difference between android reference library and java build path dependency" New topic
Author

difference between android reference library and java build path dependency

Jeff Verdegan
Bartender

Joined: Jan 03, 2004
Posts: 6109
    
    6

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.

2) Java 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: http://aspose.com/file-tools
 
subject: difference between android reference library and java build path dependency