Lines Matching full:build
22 <title>Android Build System</title>
72 <h1><a name="My_Project_" />Android Build System</h1>
86 <p>The primary goals of reworking the build system are (1) to make dependencies
88 improve performance of the build system so that unnecessary modules are not
89 rebuilt, and so doing a top-level build when little or nothing needs to be done
90 for a build takes as little time as possible.</p>
96 <p>It needs to be possible to build the Android platform for multiple targets.
99 <li>The build system will support building tools for the host platform,
100 both ones that are used in the build process itself, and developer tools
102 <li>The build system will need to be able to build tools on Linux
105 <li>The build system will need to be able to build the OS on Linux, and in
112 <p>To achieve the objectives, the build system will be rewritten to use make
151 <p>The default of the build system will be to hide the command lines being
159 current directory being set to the root of the build tree.<p>
193 problem is that this can create extra dependecies and slow down the build.
200 or environment variables need to be updated before each build. (from fadden)</p>
208 <p>You've read (or scrolled past) all of the motivations for this build system,
211 <h3>Your first build</h3>
215 <h3>build/envsetup.sh functions</h3>
216 If you source the file build/envsetup.sh into your bash environment,
217 <code>. build/envsetup.sh</code>you'll get a few helpful shell functions:
231 <h3>Build flavors/types</h3>
234 variations on what is ultimately the final release build. These are the
295 If you build one flavor and then want to build another, you should run
303 <p>Sometimes you want to just build one thing. The following pseudotargets are
307 <li><b>droid</b> - <code>make droid</code> is the normal build. This target
311 include the "droid" tag. The build server runs this to make sure
329 which causes the build system to show the actual command lines for the build
333 of targets you build. For example <code>make showcommands</code> will build
335 will build just the runtime, and targets that it depends on, while displaying
339 <a href="mailto:android-build-team">android-build-team</a> know if you find
351 <h3><a name="templates"/>How to add another component to the build - Android.mk templates</h3>
406 to have the build system get the dependencies correct for it. Here are
463 is a list of which values the different build-system defined variables will be
465 <p>For a device build, <code>TARGET_OS</code> is <code>linux</code> (we're using
467 <p>For a simulator build, <code>TARGET_OS</code> and <code>TARGET_ARCH</code>
544 build somewhere else, read this. One use of this is putting files on
555 places to build things.</p>
580 the build system, so you shouldn't create variables named like this, and
591 remember that this is a non-recursive build system, so it is possible that
601 <p>This will probably change when we switch to ant for the apps' build
730 that are not part of the build for your executable or library. Specify
749 to an ant-based build system for the apps.</p>
794 <p>The build system looks at <code>LOCAL_SRC_FILES</code> to know what source
816 is "libkjs" (the build system adds the appropriate suffix -- .so .dylib .dll).
822 <p>Instructs the build system to put the module somewhere other than what's
830 <p>Instructs the build system to put the unstripped version of the module
857 build system. In general, please consult with the build system owner(s)
858 (<a href="mailto:android-build-team">android-build-team</a>) before you go
863 <p>In order to make easier for people when the build system changes, when
866 BUILD_ENV_SEQUENCE_NUMBER. If this variable does not match what the build
876 The scripts automatically get the value from the build system, so they will
882 <a href="mailto:android-build-team">android-build-team</a> before using them.
914 <p>Used in some stuff remaining from the openbinder build system that we
