PermaLink Android Referenced Libraries can't be on different drive/partition from your Eclipse Projects07/12/2013 04:31 PM
This bit me again so I thought I'd blog about it in case anyone else hits it.  Up to now, there hasn't been that many reasons to use Android libraries unless you're using Android Bar Sherlock, but that library was something you usualy stuck in your workspace anyways (I didn't initially and got bit a few years ago).  Since Google has been putting new functionality into the Play Services Library, it's biting more people in the *ss.

Most people have been bit when trying to use Google's new Maps V2 API on Android because that functionality is now bundled/upgraded as part of their Play store. The symptom is when you're trying to use the library in your project in Eclipse, you click on ProjectProperties/Android/Library (don't use the Java Build Path) then add the project and it happily adds it with a green checkmark next to it:

However, if you go look at it again, that green checkmark becomes a red X and the reference is a full DOS path; if you look at your Java Build Path and the Android Private Libraries, you'll also notice the google-play-services_lib is also missing but the support library is there.

The workaround is during the project import of the Play Services library, make sure you click on the "Copy into workspace" checkbox:


If Play Services ever gets updated, you'll have to delete/import the library into your workspace again unless Google fixes this bug in the Eclipse ADT plugin. If you want this fixed, please star Android Issue 27199. It's been mentioned multiple times on StackOverflow also.

Comments :v
No comments.

Start Pages
RSS News Feed RSS Comments Feed CoComment Integrated
The BlogRoll
Calendar
June 2024
Su
Mo
Tu
We
Th
Fr
Sa
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Search
Contact Me
About Ken
Full-stack developer (consultant) working with .Net, Java, Android, Javascript (jQuery, Meteor.js, AngularJS), Lotus Domino