diff options
Diffstat (limited to 'docs/markdown/Precompiled-headers.md')
| -rw-r--r-- | docs/markdown/Precompiled-headers.md | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/markdown/Precompiled-headers.md b/docs/markdown/Precompiled-headers.md index 05b50bc..8b7f58e 100644 --- a/docs/markdown/Precompiled-headers.md +++ b/docs/markdown/Precompiled-headers.md @@ -40,9 +40,9 @@ Toggling the usage of precompiled headers If you wish to compile your project without precompiled headers, you can change the value of the pch option by passing `-Db_pch=false` -argument to Meson at configure time or later with `meson configure`. You can -also toggle the use of pch in a configured build directory with the -GUI tool. You don't have to do any changes to the source +argument to Meson at configure time or later with `meson configure`. +You can also toggle the use of pch in a configured build directory +with the GUI tool. You don't have to do any changes to the source code. Typically this is done to test whether your project compiles cleanly without pch (that is, checking that its #includes are in order) and working around compiler bugs. @@ -51,11 +51,11 @@ Using precompiled headers with GCC and derivatives -- Once you have a file to precompile, you can enable the use of pch for -a given target with a *pch* keyword argument. As an example, let's assume -you want to build a small C binary with precompiled headers. -Let's say the source files of the binary use the system headers `stdio.h` -and `string.h`. Then you create a header file `pch/myexe_pch.h` with this -content: +a given target with a *pch* keyword argument. As an example, let's +assume you want to build a small C binary with precompiled headers. +Let's say the source files of the binary use the system headers +`stdio.h` and `string.h`. Then you create a header file +`pch/myexe_pch.h` with this content: ```c #include <stdio.h> |