Lines Matching +full:- +full:- +full:set +full:- +full:config

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
140 set of dynamic iconv synced between the source files and configure.
148 a new file, it must be manually included -- there is no mechanism to search
157 with the historical top-level acinclude.m4 file!
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
172 part of the standard set of headers. Critically, all symbols are namespaced
179 all of Newlib using non-recursive make (i.e., there are no subdirectories with
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
209 set of flags (e.g. CFLAGS, CPPFLAGS, etc...) that are supported.
214 Per-file compiler settings are allowed. Similar to the syntax used
216 set of flags (e.g. CFLAGS, CPPFLAGS, etc...) that are supported.
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
251 it would be difficult to find the set of options necessary to produce the
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