diff options
-rw-r--r-- | docs/markdown/Meson-design-rationale:-A-proposal-for-a-better-cross-platform-build-system.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/markdown/Meson-design-rationale:-A-proposal-for-a-better-cross-platform-build-system.md b/docs/markdown/Meson-design-rationale:-A-proposal-for-a-better-cross-platform-build-system.md index 9636238..3a7e88d 100644 --- a/docs/markdown/Meson-design-rationale:-A-proposal-for-a-better-cross-platform-build-system.md +++ b/docs/markdown/Meson-design-rationale:-A-proposal-for-a-better-cross-platform-build-system.md @@ -105,7 +105,7 @@ foolib = shared_library('foobar', sources : 'foobar.c',\ exe = executable('testfoobar', 'tester.c', link : foolib) add_test('test library', exe)` -First we build a shared library named foobar. It is marked installable, so running `ninja install` installs it to the library directory (the system knows which one so the user does not have to care). Then we build a test executable which is linked against the library. It will no tbe installed, but instead it is added to the list of unit tests, which can be run with the command `ninja test`. +First we build a shared library named foobar. It is marked installable, so running `ninja install` installs it to the library directory (the system knows which one so the user does not have to care). Then we build a test executable which is linked against the library. It will not be installed, but instead it is added to the list of unit tests, which can be run with the command `ninja test`. Above we mentioned precompiled headers as a feature not supported by other build systems. Here's how you would use them. |