Lines Matching full:project
11 <li><a href="#CreatingAProject">Creating an Android Project</a></li>
12 <li><a href="#UpdatingAProject">Updating a Project</a></li>
13 <li><a href="#SettingUpLibraryProject">Setting up a Library Project</a>
16 <li><a href="#UpdatingLibraryProject">Updating a library project</a></li>
19 <li><a href="#ReferencingLibraryProject">Referencing a Library Project</a>
39 projects. An Android project contains all of the files and resources that are needed to build a
40 project into an .apk file for installation.
43 <li>An Android project contains all of the files and resources that are needed to build a project into
44 an .apk file for installation. You need to create an Android project for any application that you
47 <li>You can also designate an Android project as a library project, which allows it to be shared
48 with other projects that depend on it. Once an Android project is designated as a library
49 project, it cannot be installed onto a device.</li>
52 more information on creating a test project, see <a href=
57 <h2 id="CreatingAProject">Creating an Android Project</h2>
59 <p>To create an Android project, you must use the <code>android</code> tool. When you create a
60 new project with <code>android</code>, it will generate a project directory with some default
63 <p>To create a new Android project, open a command-line, navigate to the <code>tools/</code>
66 android create project \
69 --path path/to/your/project \
77 build your project against. To see a list of available targets and their corresponding IDs,
80 <li><code>name</code> is the name for your project. This is optional. If provided, this name
83 <li><code>path</code> is the location of your project directory. If the directory does not
91 <li><code>package</code> is the package namespace for your project, following the same rules as
97 android create project \
105 <p>Once you've created your project, you're ready to begin development. You can move your project
109 later). So you need access between your project solution and the <code>platform-tools/</code> folder.</p>
116 If you need to update the SDK location, use the <code>android update project</code> command.
117 See <a href="#UpdatingAProject">Updating a Project</a> for more information.</p>
119 <h2 id="UpdatingAProject">Updating a Project</h2>
121 <p>If you're upgrading a project from an older version of the Android SDK or want to create a new
122 project from existing code, use the <code>android update project</code> command to update the
123 project to the new development environment. You can also use this command to revise the build
124 target of an existing project (with the <code>--target</code> option) and the project name (with
127 for the Android project.</p>
129 <p>To update an existing Android project, open a command-line and navigate to the
132 android update project --name <project_name> --target <target_ID>
139 build your project against. To see a list of available targets and their corresponding IDs,
142 <li><code>path</code> is the location of your project directory.</li>
144 <li><code>name</code> is the name for the project. This is optional—if you're not
145 changing the project name, you don't need this.</li>
150 android update project --name MyApp --target 2 --path ./MyAppProject
153 <h2 id="SettingUpLibraryProject">Setting up a Library Project</h2>
155 <p>A library project is a standard Android project, so you can create a new one in the same way
156 as you would a new application project. Specifically, you can use the <code>android</code> tool
157 to generate a new library project with all of the necessary files and folders.</p>
159 <p>To create a new library project, navigate to the <code><sdk>/tools/</code> directory and
162 android create lib-project --name <your_project_name> \
164 --path path/to/your/project \
168 <p>The <code>create lib-project</code> command creates a standard project structure that includes
169 preset property that indicates to the build system that the project is a library. It does this by
170 adding this line to the project's <code>project.properties</code> file:</p>
175 <p>Once the command completes, the library project is created and you can begin moving source
178 <p>If you want to convert an existing application project to a library project, so that other
180 to the application's <code>project.properties</code> file.</p>
184 <p>A library project's manifest file must declare all of the shared components that it includes,
190 project declares the Activity <code>GameActivity</code>:</p>
202 <h3 id="UpdatingLibraryProject">Updating a library project</h3>
204 <p>If you want to update the build properties (build target, location) of the library project,
207 android update lib-project \
209 --path <em>path/to/your/project</em>
212 <h2 id="ReferencingLibraryProject">Referencing a Library Project</h2>
215 library project, you can do so easily by adding a reference to the library project in the
216 application project's build properties.</p>
218 <p>To add a reference to a library project, navigate to the <code><sdk>/tools/</code>
221 android update project \
223 --path <em>path/to/your/project</em>
227 <p>This command updates the application project's build properties to include a reference to the
228 library project. Specifically, it adds an <code>android.library.reference.<em>n</em></code>
229 property to the project's <code>project.properties</code> file. For example:</p>
235 priority (and merge order) by manually editing the <code>project.properties</code> file and
262 <p>In the manifest file of the application project, you must add declarations of all components
263 that the application will use that are imported from a library project. For example, you must
290 <p>To build an application project that depends on one or more library projects, you can use the
294 compiling the dependent application project. No additional commands or steps are necessary.</p>
