Lines Matching +full:runs +full:- +full:on

2 For information on using Newlib (building, installing), see README.  (In
7 initially-provided sections.  Please help by adding as appropriate.)
12      All the documentation for Newlib comes as part of the machine-readable
22 The basic function of makedoc is two-fold.  First, it recognizes comments in
26 (makedoc.c is not particularly-well commented.)  Another way to see how they
30 	libm/common/s_isnan.c ("o+" variable-"bullet" list),
35 produce both on-line information and a printed manual.  You can use one of the
36 Info formatting commands to create the on-line version of the documentation
47 when a non-printed manual is produced--such as when info pages are produced.
65 1.  Add properly-formatted comments to source file (e.g. src.c);
67     re-generate Makefile.in;
78 purpose of Linux-based open standards for embedded development.  In brief,
80 user to size the library appropriately for their application--at least in
84 is to ask Jeff Johnston.  To see how it works and try classification on your
85 own, refer to the API specification on the web site,
101 that are not easily implemented on an RTOS.  Also full implementations of
148   a new file, it must be manually included -- there is no mechanism to search
157   with the historical top-level acinclude.m4 file!
160 usually runs with a toolchain that lacks a C library (since Newlib will provide
165 stick to the appropriate source-level test -- AC_PREPROC for testing behavior
171 declares all the Newlib-specific configure settings and will be installed as
179 all of Newlib using non-recursive make (i.e., there are no subdirectories with
184 like "SOURCES" in any Makefile.inc file.  Instead, use %C%_ on all variables to
193 to iterate quickly on a smaller section of Newlib might be surprised that this
194 does not work -- there is no Makefile in any subdirectory.  Instead, make has
195 to be run from the top-level, and the full path to the target is specified.
207      Per-directory compiler settings are allowed.  Similar to the syntax used
214      Per-file compiler settings are allowed.  Similar to the syntax used
221      An important aspect of the build system is allowing machine-specific
228 common object is added first, followed by the machine-specific one.  This works
229 because the object names follow a consistent convention: libm_a-<filename>.o
230 for the math library and libc_a-<filename>.o for the C library.  If the common
238 to the corresponding source directory, but that is it.  For more details on
250 at all times.  If inclusion of chapters depended on specific configure options,
264 * ../config/multi.m4: AM_ENABLE_MULTILIB adds the --{en,dis}able-multilib
265   options to configure for users, and takes care of calling ../config-ml.in
270 * ../config-ml.in: Rewrites the specified Makefile to include the various
271   multilib variables and the multi-do command.  Notably, this only makes the
272   multi-do rule available, it does not cause it to be used anywhere.
274   to multi-do for the common important rules: all (i.e. compiling), install,
277   each multilib configuration via the multi-do rule.  While the multi-do rule