Lines Matching refs:build

16 Subject: How to build an Android SDK & ADT Eclipse plugin.
55 This document explains how to build the Android SDK and the ADT Eclipse plugin.
80 Then once you have all the source, simply build the SDK using:
83   $ . build/envsetup.sh
90   Package SDK: out/host/darwin-x86/sdk/android-sdk_eng.<build-id>_mac-x86.zip
94 - Depending on your machine you can tell 'make' to build more things in
95   parallel, e.g. if you have a dual core, use "make -j4 sdk" to build faster.
97 - You can define "BUILD_NUMBER" to control the build identifier that gets
103   There are certain characters you should avoid in the build number, typically
115 SDK is build on top of a Linux SDK where a few binaries are replaced. So it
120   To build the Android SDK for Windows, you need to use a *Linux* box.
128 setup and build a regular Linux SDK. Once this working, please continue here.
140 To build, perform the following steps:
142 $ . build/envsetup.sh
146 Note that this will build both a Linux SDK then a Windows SDK.
154 You can also build isolated windows tools directly on Linux without building
157 To build, perform the following steps:
160   $ . build/envsetup.sh
182 build script by giving it a destination directory and an optional build number:
191 Eclipse build fail with a cryptic message:
199 The second argument is the build "number". The example used "$USER" but it
201 periods (dashes are ok.) If the build number is missing, a build timestamp will
204 The build should take something like 5-10 minutes.
207 When the build succeeds, you'll see something like this at the end of the
216 internal plugin ID is always composed of the package, the build timestamp and
217 then your own build identifier (a.k.a. the "build number"), if provided. This
218 means successive builds with the same build identifier are incremental and