Eclipse Android SDK slow Content Assist performance

前端 未结 4 1762
暖寄归人
暖寄归人 2020-12-02 21:06

Im running eclipse on my windows 7 machine, 64bit with 6gb ram and core 2 duo. Im currently running Eclipse 3.6 and android 2.2 SDK Im running jdk 1.6

Im noticing th

相关标签:
4条回答
  • 2020-12-02 21:33

    This is much better Eclipse autocompletion problem

    0 讨论(0)
  • 2020-12-02 21:42

    here is a link for the problem you are having

    http://aaarkonusurum.blogspot.com/2011/08/eclipse-intelisensein-cldrtan-yavaslgna.html

    0 讨论(0)
  • 2020-12-02 21:54

    After a google search

    I have been able to find the bug report from Eclipse.

    In short:

    • It is a problem that arises when using Helios with ADT. As the ADT page on android.com says:

    Caution: There are known issues with the ADT plugin running with Eclipse 3.6. Please stay on 3.5 until further notice.

    • To fix it, you will have to use Eclipse 3.5 and put your project in a newly created workspace. (If you keep the workspace from Eclipse 3.6, the problem will occur even on Eclipse 3.5.)
    0 讨论(0)
  • 2020-12-02 21:55

    A Work-around procedure is presented in comment#8 at this URL: http://code.google.com/p/android/issues/detail?id=7850

    Example:

    I'm coding against Froyo, and my target SdkVersion is 7 (AndroidManifest.xml). So for step 1, I downloaded this file:

    https://android.googlesource.com/platform/frameworks/base/+archive/froyo-release.tar.gz
    

    And then for step 2, I extracted the base/ directory of that .tgz file into my SDK path, which I install under /opt/android-sdk-linux_x86/. So here's the command I executed against the tgz to put everything where it goes:

    tar -vzxf base-froyo.tar.gz -C /opt/android-sdk-linux_x86/platforms/android-7/sources/ base/
    

    The end goal appears to be to place the actual sources into the "sources" folder in the SDK tree, so that when the auto-correct goes out looking for them, they are there.

    snpe60 describes it more clearly:

    Comment 7 by snpe60, Oct 14, 2010 This issue is happen because the ADT classpath container have an invalid source attachment by default. It is fixed in https://review.source.android.com/16569. This change enables changing the ADT clasppath container's source attachment and disables setting invalid source attachment. Hoping it will be available in ADT 8.0.0.

    0 讨论(0)
提交回复
热议问题