Browsing Android(安卓)Source in Eclipse

Google’s Android SDK includes android.jar, which contains the Android public API class files. They also provide an Eclipse plugin, making it quite easy to get started. What you will not find, however, is androidSrc.jar, so when you try to look at Android SDK source code in Eclipse, you get something like this:

Open Source to the Rescue!

Earlier this month, Google released the source code — all of it — and by the way, it’s HUGE. Anyway, to browse source in Eclipse, you need to visit http://source.android.com/ and follow their instructions to pull everything down using Git. Set aside an evening to do this, because having the full source makes it infinitely easier to understand how the SDK works.

Attaching to Eclipse…Not So Fast, Buddy

Now that you have the source, you can tell Eclipse where to find it. I tried right-clicking on android.jar and selecting Properties, but am greeted with this screen:

Hmm…”The current class path entry belongs to container ‘Android Library’ which does not allow user modifications to source attachments on its entries.” This really threw me for a loop. I generally use IDEA, so I was really stumped by this. So, I dug into the source code to find out a solution.

Examining the Source

When you download the Android source, you get EVERYTHING. This includes the OS, the Dalvik VM, the Eclipse Plugin, the public SDKs, etc.

In the com.android.ide.eclipse.adt.project.internal package, I found
a class named AndroidClassspathContainerInitializer.java. This has
the following code:

IPath android_src = new Path(AdtPlugin.getOsAbsoluteAndroidSources());

OK, fine. So looking inside AdtPlugin.java:

/** Returns the absolute android sources path in the sdk */public static String getOsAbsoluteAndroidSources() {  return getOsSdkFolder() + getOsRelativeAndroidSources();}/** Returns the android sources path relative to the sdk folder */public static String getOsRelativeAndroidSources() {  return AndroidConstants.FD_ANDROID_SOURCES;}

And finally inside AndroidConstants.java:

public static final String FD_ANDROID_SOURCES = "sources";

I win!

Solution #1

Based on the above analysis, you need to create a directory named “sources” inside your Android SDK installation. So right next to your android.jar, create a sources directory.

Now that you have this directory, you can find the appropriate source directories in the Android sources that you pulled from Git. Google’s checkout directions suggest a directory named ‘mydroid’, so I’ll use that here. The public SDK source is found in mydroid/frameworks/base/core/java. Under that folder you’ll find an android directory, which should be copied (or symlinked) over to the sources directory in your SDK installation.

You’ll have to do some hunting around to find all of the source code, it’s kind of sprinkled all over the place in the mydroid directory tree. In the end, you should have something like:

SDK_PATH  | android.jar  +--docs/...  +--samples/...  +--sources       +--android       |      ...accounts, annotation, app, bluetooth, etc...       +--com/android/etc...       +--dalvik/...       +--java/...       +--javax/...

I grabbed all kinds of directories, and I didn’t take good notes, so I probably missed a few and inadvertently added too many. You probably only really need the public SDK sources, but I think it’s nice to also study implementation classes, as well.

Now when I browse into the Android SDK classes, I see the source code:

Solution #2

If you’d rather not copy (or link) all of those source directories into your SDK directory, you can also create an Eclipse User Library. At first, I tried creating my own library containing android.jar, but Eclipse complained about that being a duplicate .jar file. So instead, I picked an arbitrary JAR file as my user library, and then proceeded to attach all of the Android source directories to that library.

My user library seemed to do the trick, but I like having that sources directory because I don’t have to remember to add the user library to each new project I create.

Posted on Saturday, November 1st, 2008 at 10:20 pm in Android.

kiran Says:

Good job on writing this.
Google did a really bad job on the api docs.. I am glad the source will alleviate the pain of the missing docs.
btw, have you had any luck with getting the VideoView working on the real phone or the emulator.

November 3rd, 2008 at 11:55 am     wdf Says:

It doesn’t work at all, and just see .class

November 18th, 2008 at 4:58 am     wdf Says:

When I copied (not symlinked) over to the sources directory, it works, thanks a lot!

November 18th, 2008 at 5:05 am     apple Says:

Which files did you copy exactly? I tried both symlink and copy and still doesn’t work. I copied
~/myandroid/frameworks/base/core/java/android/

Tried to view Activity.class from Eclipse and had the same error.

$ cd ~/android-sdk-linux_x86-1.0_r1/sources
$ cp -rf ~/myandroid/frameworks/base/core/java/android/ .
$ ls
android
$ ls android
accounts app content ddm hardware os pim provider server syncml text view widget
annotation bluetooth database debug net package.html preference security speech test util webkit

November 20th, 2008 at 8:51 pm     Wazabe Says:

Sweet as hell, thank you so much for sharing this killer tip !

November 21st, 2008 at 12:13 pm     Josh Guilfoyle Says:

Just as a tip for anyone reading, you must hit Refresh on the Android library in Eclipse to make this work. Even if you restart Eclipse.

November 22nd, 2008 at 12:50 am     apple Says:

Refresh did the trick! Thank you Josh.

December 1st, 2008 at 8:55 pm     LeConcombreMasque Says:

I also found this documented at http://ralf.alfray.com/.izumi/AndroidTips.blog (scroll down)

December 2nd, 2008 at 1:00 pm     davemepp Says:

Thanks for the helpful post, Eric.

I used http://androidforums.com/showthread.php?t=1045 to create android-src.jar and then extracted the jar to ANDROID_HOME\sources, and it worked like a charm.

December 5th, 2008 at 4:21 pm     Michael Forster Says:

Collecting all of the *.java files from the Android source tree to the right place is a lot of work. Here is a small script that I wrote to build a source ZIP: http://blog.michael-forster.de/2008/12/view-android-source-code-in-eclipse.html

December 20th, 2008 at 12:09 pm     Robert Zaleski Says:

I had problems getting this to work until I used the rsync line on the ralf site to copy everything. It may have worked sym linking everything too, but it must either be that I didn’t refresh right, or there was a certain file I needed. But it’s good to know I can browse source now. Thanks for the info.

December 20th, 2008 at 2:25 pm     boyb Says:

In Eclips, i want to see the souce code for “Android Liabrary->res.layout-simple_list_item_1.xml” or something like that, when double click the item, eclips could not open it. If right click the item and choose to see property, it prompt “no property pages for”, but i could see the souce code for Activity.classs.
I have already copy folder andoid(including accounts/anotation…)? And i find some folder …apps/common/res/layout contain those xml, so i also copy apps to andoid folder and click to refresh the sdk in Eclips, but still could not see the souce.

What else should i do to view souce code of those xml file?Thanks

December 21st, 2008 at 9:05 am     Uhyon Chung Says:

You might also want to make sure your SDK Location contains a final slash (or backslash in Windows). Or else, it won’t find your sources since the append in getOsAbsoluteAndroidSources does add a slash itself.

March 17th, 2009 at 10:55 pm     sudheer Says:

I tried all the steps mentioned above. But I am not able to see every thing even now. For e.g. I am not able to see the surface manager class in android.os .but its present in the relevant directory. I am not able to see that in eclipse. Can some one tell me what could be the problem?

What I did
1. created sources directory
2. copied android folder from /framework/core/.. to sources
3. copied all other java files to sources
4. refreshed/restarted eclipse

Did I miss any thing?

March 19th, 2009 at 3:19 am     Ty Says:

The slash was the culprit for me (Mac OS-X, Ganymede). The android SDK path defaults to no slash, so the default path formed is incorrect.
Eclipse > Preferences > Android > SDK Location

April 16th, 2009 at 11:40 am     Sharad Says:

I observed that instead of “source” folder it was “sources” folder in 1.5 SDK, if you are not sure on what name you should give to the folder then just goto the build path of the project (Right click Android project -> Properties) and expand Android 1.1 and then Android.jar, you should see source attachment path with should exactly match the path where you are keeping the source code. Once this is set just restart eclipse and you are done.

May 15th, 2009 at 4:50 pm     Rick Bing Says:

Great job. You are Numero Uno.

May 19th, 2009 at 4:28 pm     Donald B. Says:

Thanks, this is very helpful.

I had to create the symlinks in the appropriate plaforms/android-1.x directory to get this to work for me.

My SDK:
~/apps/android-sdk-linux_x86-1.5_r2/

But my android.jar file is here:
~/apps/android-sdk-linux_x86-1.5_r2/platforms/android-1.1

May 24th, 2009 at 6:05 pm     mefiX Says:

With Android 1.5 i had to place the “sources”-folder into
/platforms/android-1.5
Eventually a refresh of the project revealed the source-files.

May 26th, 2009 at 5:01 am     Jn Says:

Thanks a lot!

June 9th, 2009 at 4:45 am     Manjunath Says:

This is some thing which i was looking form past many days! thanks a lot. bravo.

August 10th, 2009 at 9:32 pm     stanlick Says:

Well, I have the source showing up on one machine but not another. The machine that does not show source, is effectively a clone of the machine which works ! What exactly are you refreshing when you mention refreshing the Android library in Eclipse?

Peace,
Scott

August 25th, 2009 at 10:56 am

Follow It’s Just a Bunch of Stuff That Happens via the Entries and Comments Atom feeds.

<script type="text/javascript"></script><script src="http://www.google-analytics.com/ga.js" type="text/javascript"></script><script type="text/javascript"></script>

Open Source to the Rescue!

Attaching to Eclipse…Not So Fast, Buddy

Examining the Source

Solution #1

Solution #2

更多相关文章

随机推荐