diff options
Diffstat (limited to 'docs/markdown/Include-directories.md')
-rw-r--r-- | docs/markdown/Include-directories.md | 17 |
1 files changed, 13 insertions, 4 deletions
diff --git a/docs/markdown/Include-directories.md b/docs/markdown/Include-directories.md index c1d4ac12d..6dfed5e48 100644 --- a/docs/markdown/Include-directories.md +++ b/docs/markdown/Include-directories.md @@ -4,18 +4,27 @@ short-description: Instructions on handling include directories # Include directories -Most `C`/`C++` projects have headers in different directories than sources. Thus you need to specify include directories. Let's assume that we are at some subdirectory and wish to add its `include` subdirectory to some target's search path. To create a include directory object we do this: +Most `C`/`C++` projects have headers in different directories than +sources. Thus you need to specify include directories. Let's assume +that we are at some subdirectory and wish to add its `include` +subdirectory to some target's search path. To create a include +directory object we do this: ```meson incdir = include_directories('include') ``` -The `incdir` variable now holds a reference to the `include` subdir. Now we pass that as an argument to a build target: +The `incdir` variable now holds a reference to the `include` subdir. +Now we pass that as an argument to a build target: ```meson executable('someprog', 'someprog.c', include_directories : incdir) ``` -Note that these two commands can be given in any subdirectories and it will still work. Meson will keep track of the locations and generate proper compiler flags to make it all work. +Note that these two commands can be given in any subdirectories and it +will still work. Meson will keep track of the locations and generate +proper compiler flags to make it all work. -Another thing to note is that `include_directories` adds both the source directory and corresponding build directory to include path, so you don't have to care. +Another thing to note is that `include_directories` adds both the +source directory and corresponding build directory to include path, so +you don't have to care. |