summaryrefslogtreecommitdiff
path: root/docs/markdown/Using-with-Visual-Studio.md
diff options
context:
space:
mode:
authorJussi Pakkanen <jpakkane@gmail.com>2021-01-30 13:20:59 +0200
committerJussi Pakkanen <jpakkane@gmail.com>2021-01-30 13:26:57 +0200
commit708b83a029b1c2ae91ad6426d45b6723893e1427 (patch)
treeedf5bd6e1cccc01f57572620d96beeafbbe3a175 /docs/markdown/Using-with-Visual-Studio.md
parentf0fbb31ccfa78ca1d7b7f9cedfbb090bf36d3e64 (diff)
downloadmeson-docrewrap.tar.gz
Rewrap long text lines in docs. [skip ci]docrewrap
Diffstat (limited to 'docs/markdown/Using-with-Visual-Studio.md')
-rw-r--r--docs/markdown/Using-with-Visual-Studio.md22
1 files changed, 12 insertions, 10 deletions
diff --git a/docs/markdown/Using-with-Visual-Studio.md b/docs/markdown/Using-with-Visual-Studio.md
index c66cf3c6f..3c97ee556 100644
--- a/docs/markdown/Using-with-Visual-Studio.md
+++ b/docs/markdown/Using-with-Visual-Studio.md
@@ -4,22 +4,24 @@ short-description: How to use meson in Visual Studio
# Using with Visual Studio
-In order to generate Visual Studio projects, Meson needs to know the settings
-of your installed version of Visual Studio. The only way to get this
-information is to run Meson under the Visual Studio Command Prompt.
+In order to generate Visual Studio projects, Meson needs to know the
+settings of your installed version of Visual Studio. The only way to
+get this information is to run Meson under the Visual Studio Command
+Prompt.
-You can always find the Visual Studio Command Prompt by searching from the
-Start Menu. However, the name is different for each Visual Studio version. With
-Visual Studio 2019, look for "x64 Native Tools Command Prompt for VS 2019".
-The next steps are [the same as always](https://mesonbuild.com/Running-Meson.html#configuring-the-build-directory):
+You can always find the Visual Studio Command Prompt by searching from
+the Start Menu. However, the name is different for each Visual Studio
+version. With Visual Studio 2019, look for "x64 Native Tools Command
+Prompt for VS 2019". The next steps are [the same as
+always](https://mesonbuild.com/Running-Meson.html#configuring-the-build-directory):
1. `cd` into your source directory
1. `meson setup builddir`, which will create and setup the build directory
1. `meson compile -C builddir`, to compile your code. You can also use `ninja -C builddir` here if you are using the default Ninja backend.
-If you wish to generate Visual Studio project files, pass `--backend vs`.
-At the time of writing the Ninja backend is more mature than the VS backend so
-you might want to use it for serious work.
+If you wish to generate Visual Studio project files, pass `--backend
+vs`. At the time of writing the Ninja backend is more mature than the
+VS backend so you might want to use it for serious work.
# Using Clang-CL with Visual Studio