Home | History | Annotate | Download | only in source

Lines Matching full:eclipse

17 # Using Eclipse #
19 This document will help you set up the Eclipse IDE for Android platform development.
22 Eclipse to develop applications that run on Android, this is not the right
23 page for you. You probably would find [the Eclipse page on
24 developer.android.com](http://developer.android.com/sdk/eclipse-adt.html) more useful.*
33 **Important**: You will still be using `make` to build the files you will actually run (in the emulator or on a device). You will be using Eclipse to edit files and verify that they compile, but when you want to run something you will need to make sure files are saved in Eclipse and run `make` in a shell. The Eclipse build is just for error checking.
35 Eclipse needs a list of directories to search for Java files. This is called the "Java Build Path" and can be set with the `.classpath` file. We have a sample version to start you off.
38 cp development/ide/eclipse/.classpath .
43 ### Increase Eclipse's Memory Settings ###
45 The Android project is large enough that Eclipse's Java VM sometimes runs out of memory while compiling it. Avoid this problem by editing the the `eclipse.ini` file. On Apple OSX the eclipse.ini file is located at
47 /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse.ini
49 Memory-related defaults (as of Eclipse 3.4):
61 These settings set Eclipse's minimum Java heap size to 128MB, set the maximum Java heap size to 512MB, and keep the maximum permanent generation size at the default of 256MB.
63 Now start Eclipse:
65 eclipse
69 1. If Eclipse asks you for a workspace location, choose the default.
81 Once the project workspace is created, Eclipse should start building. In theory, it should build with no errors and you should be set to go. If necessary, uncheck and re-check Project Build Automatically to force a rebuild.
83 *Note:* Eclipse sometimes likes to add an `import android.R` statement at the top of your files that use resources, especially when you ask eclipse to sort or otherwise manage imports. This will cause your make to break. Look out for these erroneous import statements and delete them.
87 Every time you repo sync, or otherwise change files outside of Eclipse (especially the .classpath), you need to refresh Eclipse's view of things:
97 The default `.classpath` includes the source to the core system and a sample set of apps, but might not include the particular app you may want to work on. To add an app, you must add the app's source directory. To do this inside Eclipse:
117 ## Eclipse formatting ##
119 You can import files in `development/ide/eclipse` to make Eclipse
128 ## Debugging the emulator with Eclipse ##
130 You can also use eclipse to debug the emulator and step through code. First, start the emulator running:
147 Now, in eclipse, you can attach to the emulator:
180 ## Eclipse is not working correctly, what should I do? ##