1## Building for the local processor
2
3If you want to compile the library for your local processor to test
4changes in the library, the meson configuration is happy to do that
5for you. You won't need a meson cross compilation configuration file,
6so all you need is the right compile options. They're mostly the same
7as the embedded version, but you don't want the multi-architecture
8stuff and I prefer plain debug to an -Os, as that makes debugging the
9library easier.
10
11The do-native-configure script has an example:
12
13    #!/bin/sh
14    DIR=`dirname $0`
15    meson $DIR \
16	    -Dmultilib=false \
17	    -Dnewlib-wide-orient=false\
18	    -Dnewlib-nano-malloc=true\
19	    -Dlite-exit=true\
20	    -Dnewlib-global-atexit=true\
21	    -Dincludedir=lib/newlib-nano/include \
22	    -Dlibdir=lib/newlib-nano/lib \
23	    -Dtests=true \
24	    --buildtype debug
25
26Again, create a directory and build there:
27
28    $ mkdir build-native
29    $ cd build-native
30    $ ../do-native-configure
31    $ ninja
32
33This will also build a test case for printf and scanf in the
34'test' directory, which I used to fix up the floating point input and
35output code.
36