Lines Matching full:will
18 Your readers will be very appreciative.
94 that we will support. This is not an exhaustive list.</p>
99 <li>The build system will support building tools for the host platform,
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
126 in one terminal. We will support both.</p>
128 <p>Object files and other intermediate files will be generated into a directory
135 <p>The SDK will be a tarball that will allow non-OS-developers to write apps.
136 The apps will actually be built by first building the SDK, and then building
137 the apps against that SDK. This will hopefully (1) make writing apps easier
142 figure out exactly how this will work.</p>
151 <p>The default of the build system will be to hide the command lines being
152 executed for make steps. It will be possible to override this by specifying
157 <p>Wildcarding source file will be discouraged. It may be useful in some
158 scenarios. The default <code>$(wildcard *)</code> will not work due to the
162 <p>It will be possible to generate more than one target from a given
203 <p>We will eventually need to add support for creating locales and carrier
204 customizations to the SDK, but that will not be addressed right now.</p>
298 clean</code>" will also suffice, but it takes a lot longer.
315 <code>make clean-libutils</code> and it will delete libutils.so and all of the
316 intermediate files, or you can type <code>make clean-Home</code> and it will
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
347 <li><b>targets</b> - <code>make targets</code> will print a list of all of
354 directory. It will usually be enough to copy one of these, and fill in your
374 what you put in LOCAL_MODULE). This name will be what goes in the
463 is a list of which values the different build-system defined variables will be
472 that will happen here, but likely there will be additional UI configurations
520 <code>TARGET_SIMULATOR</code> will be set to <code>true</code>.
558 will force the linker to only accept static libraries.</p>
577 PRIVATE_. It is safe, and they will be fixed as they are discovered.
592 your variable will be changed by another Android.mk included later, and be
601 <p>This will probably change when we switch to ant for the apps' build
637 is non-empty, none of the default includes or flags will be used when compiling
640 <code>LOCAL_CPPFLAGS</code> will still be used in this case, as will
644 <p class=warning>This will be going away.</p>
654 <p class=warning>This will be going away.</p>
684 will get installed as part of a <code>make droid</code>. Otherwise, it will
691 of the modules that it requires will be installed as well. This can be
702 <p>Files that you add to <code>LOCAL_GENERATED_SOURCES</code> will be
716 In most cases, it will look like this:</p>
721 will be included automatically.</p>
732 link line. However, keep in mind that there will be no dependency generated
748 Dialer, Contacts, etc. This will probably change or go away when we switch
825 so the unstripped binary has somewhere to go. An error will occur if you forget
834 <code>LOCAL_UNSTRIPPED_PATH</code>, an error will occur.</p>
847 here is that the flags will be the same for all invocations of YACC for your
869 so this message will be printed.
876 The scripts automatically get the value from the build system, so they will
928 <p>The suffix that will be appended to <code>LOCAL_MODULE</code> to form
