Skip to content

Commit 6ca5478

Browse files
john-parjohn-par
committed
1769497, fixed typos.
1 parent 6c77df9 commit 6ca5478

15 files changed

+65
-65
lines changed

‎docs/build-insights/tutorials/wpa-basics.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,15 +36,15 @@ Most C++ Build Insights WPA views have multiple presets for you to choose from.
3636

3737
Some build traces are so large it's hard to make out the details. To zoom in on an area that interests you, right-click on the graph and select **Zoom**. You can always go back to the previous setting by choosing **Undo Zoom**. This image shows an example of using a selection and the **Zoom** command to zoom in on a section of the graph:
3838

39-
![A short video showing zooming in on a graph.](media/wpa-zooming.gif)
39+
![Short video showing zooming in on a graph.](media/wpa-zooming.gif)
4040

4141
## Group by different columns
4242

4343
You can customize the way your trace is displayed. Click on the gear icon at the top of a view pane and rearrange the columns in the Build Explorer View Editor. The columns found above the yellow line in this dialog are the ones your data rows are grouped by. The column right above the yellow line is special: in the graph view, it's displayed on the colored bars.
4444

4545
This image shows an example bar graph of a link invocation. We use the gear icon to open the Build Explorer View Editor dialog. Then we drag the Component and Name column entries above the yellow line. The configuration is changed to increase the level of detail, and to see what actually happened inside the linker:
4646

47-
![A short video showing showing how you can group by different columns.](media/wpa-grouping.gif)
47+
![Short video showing showing how you can group by different columns.](media/wpa-grouping.gif)
4848

4949
## See also
5050

‎docs/build/clang-support-cmake.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ To modify an existing configuration to use Clang, follow these steps:
5050

5151
1. Under **General** select the **Toolset** dropdown and choose the desired Clang toolset:
5252

53-
![A screenshot of the General dialog box showing that he Toolset is selected and clang cl x 86 is highlighted.](media/cmake-clang-toolset.png)
53+
![Screenshot of the General dialog box showing that the Toolset is selected and clang cl x 86 is highlighted.](media/cmake-clang-toolset.png)
5454

5555
## Custom Clang locations
5656

@@ -61,7 +61,7 @@ By default, Visual Studio looks for Clang in two places:
6161

6262
You can specify another location by setting the **CMAKE_C_COMPILER** and **CMAKE_CXX_COMPILER** CMake variables in **CMake Settings**:
6363

64-
![A screenshot of the C Make Settings dialog box with the C Make C X X Compiler highlighted.](media/clang-location-cmake.png)
64+
![Screenshot of the C Make Settings dialog box with the C Make C X X Compiler highlighted.](media/clang-location-cmake.png)
6565

6666
## Clang compatibility modes
6767

‎docs/build/clang-support-msbuild.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,13 +20,13 @@ You can use Visual Studio 2019 version 16.2 with Clang to edit, build, and debug
2020

2121
For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang tools for Windows** under **Desktop development with C++** optional components. If you prefer to use an existing Clang installation on your machine, choose the **C++ Clang-cl for v142 build tools.** optional component. The Microsoft C++ Standard Library currently requires at least Clang 8.0.0; the bundled version of Clang will automatically be updated to stay current with updates in the Microsoft implementation of the Standard Library.
2222

23-
![A screenshot of the Visual Studio installer with the Individual components tab selected and the C plus plus Clang components visible.](media/clang-install-vs2019.png)
23+
![Screenshot of the Visual Studio installer with the Individual components tab selected and the C plus plus Clang components visible.](media/clang-install-vs2019.png)
2424

2525
## Configure a Windows project to use Clang tools
2626

2727
To configure a Visual Studio project to use Clang, right-click on the project node in **Solution Explorer** and choose **Properties**. Typically, you should first choose **All configurations** at the top of the dialog. Then, under **General** > **Platform Toolset**, choose **LLVM (clang-cl)** and then **OK**.
2828

29-
![A screenshot of the Property Pages dialog box with Configuration Properties > General selected and the Platform Toolset and L L V M (clang c l) options highlighted.](media/clang-msbuild-prop-page.png)
29+
![Screenshot of the Property Pages dialog box with Configuration Properties > General selected and the Platform Toolset and L L V M (clang c l) options highlighted.](media/clang-msbuild-prop-page.png)
3030

3131
If you are using the Clang tools that are bundled with Visual Studio, no additional steps are required. For Windows projects, Visual Studio by default invokes Clang in [clang-cl](https://llvm.org/devmtg/2014-04/PDFs/Talks/clang-cl.pdf) mode and links with the Microsoft implementation of the Standard Library. By default, **clang-cl.exe** is located in *%VCINSTALLDIR%\\Tools\\Llvm\\bin\\* and *%VCINSTALLDIR%\\Tools\\Llvm\\x64\\bin\\*.
3232

‎docs/build/cmake-projects-in-visual-studio.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The **C++ CMake tools for Windows** component uses the [Open Folder](open-folder
2020

2121
**C++ CMake tools for Windows** is installed as part of the **Desktop development with C++** and **Linux Development with C++** workloads. For more information, see [Cross-platform CMake projects](../linux/cmake-linux-project.md).
2222

23-
![A screenshot of the Desktop development with C plus plus dropdown selected and the C plus plus C Make tolls for Windows option called out.](media/cmake-install-2019.png)
23+
![Screenshot of the Desktop development with C plus plus dropdown selected and the C plus plus C Make tools for Windows option called out.](media/cmake-install-2019.png)
2424

2525
For more information, see [Install the C++ Linux workload in Visual Studio](../linux/download-install-and-setup-the-linux-development-workload.md).
2626

@@ -153,7 +153,7 @@ Visual Studio 2017 has rich support for CMake, including [cross-platform CMake p
153153

154154
**Visual C++ Tools for CMake** is installed as part of the **Desktop development with C++** and **Linux Development with C++** workloads.
155155

156-
![A screenshot of the Individual components tab with the Visual C plus plus tools for C make option called](media/cmake-install.png)
156+
![Screenshot of the Individual components tab with the Visual C plus plus tools for C make option called out.](media/cmake-install.png)
157157

158158
For more information, see [Install the C++ Linux workload in Visual Studio](../linux/download-install-and-setup-the-linux-development-workload.md).
159159

‎docs/build/walkthrough-creating-and-using-a-dynamic-link-library-cpp.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ In this set of tasks, you create a project for your DLL, add code, and build it.
8383

8484
When the solution is created, you can see the generated project and source files in the **Solution Explorer** window in Visual Studio.
8585

86-
![A screenshot of the Visual Studio 2019 Solution Explorer window with the Math Library highlighted.](media/mathlibrary-solution-explorer-162.png "Generated solution in Visual Studio")
86+
![Screenshot of the Visual Studio 2019 Solution Explorer window with the Math Library highlighted.](media/mathlibrary-solution-explorer-162.png "Generated solution in Visual Studio")
8787

8888
::: moniker-end
8989

@@ -95,13 +95,13 @@ When the solution is created, you can see the generated project and source files
9595

9696
1. In the left pane of the **New Project** dialog box, select **Installed** > **Visual C++** > **Windows Desktop**. In the center pane, select **Dynamic-Link Library (DLL)**. Enter *MathLibrary* in the **Name** box to specify a name for the project. Leave the default **Location** and **Solution name** values. Set **Solution** to **Create new solution**. Check **Create directory for solution** if it's unchecked.
9797

98-
![A screenshot of the V S 2017 New Project dialog box showing Math Library in the Name text box.](media/mathlibrary-new-project-name-159.png "Name the MathLibrary project")
98+
![Screenshot of the Visual Studio 2017 New Project dialog box showing Math Library in the Name text box.](media/mathlibrary-new-project-name-159.png "Name the MathLibrary project")
9999

100100
1. Choose the **OK** button to create the project.
101101

102102
When the solution is created, you can see the generated project and source files in the **Solution Explorer** window in Visual Studio.
103103

104-
![A screenshot of the V S 2017 Solution Explorer window with the Math Library highlighted.](media/mathlibrary-solution-explorer-159.png "Generated solution in Visual Studio")
104+
![Screenshot of the Visual Studio 2017 Solution Explorer window with the Math Library highlighted.](media/mathlibrary-solution-explorer-159.png "Generated solution in Visual Studio")
105105

106106
::: moniker-end
107107

@@ -113,7 +113,7 @@ When the solution is created, you can see the generated project and source files
113113

114114
1. In the left pane of the **New Project** dialog box, expand **Installed** > **Templates**, and select **Visual C++**, and then in the center pane, select **Win32 Console Application**. Enter *MathLibrary* in the **Name** edit box to specify a name for the project. Leave the default **Location** and **Solution name** values. Set **Solution** to **Create new solution**. Check **Create directory for solution** if it's unchecked.
115115

116-
![A screenshot of the V S 2015 New Project dialog box showing Math Library in the Name text box.](media/mathlibrary-project-name.png "Name the MathLibrary project")
116+
![Screenshot of the Visual Studio 2015 New Project dialog box showing Math Library in the Name text box.](media/mathlibrary-project-name.png "Name the MathLibrary project")
117117

118118
1. Choose the **OK** button to dismiss the **New Project** dialog and start the **Win32 Application Wizard**.
119119

@@ -127,7 +127,7 @@ When the solution is created, you can see the generated project and source files
127127

128128
When the wizard completes the solution, you can see the generated project and source files in the **Solution Explorer** window in Visual Studio.
129129

130-
![A screenshot of the V S 2015 Solution Explorer window with the Math Library highlighted.](media/mathlibrary-solution-explorer-153.png "Generated solution in Visual Studio")
130+
![Screenshot of the Visual Studio 2015 Solution Explorer window with the Math Library highlighted.](media/mathlibrary-solution-explorer-153.png "Generated solution in Visual Studio")
131131

132132
::: moniker-end
133133

@@ -397,7 +397,7 @@ To avoid out-of-sync code, we recommend you set the include path in your client
397397

398398
1. In the **Configure your new project** page, enter *MathClient* in the **Project name** box to specify a name for the project. Leave the default **Location** and **Solution name** values. Set **Solution** to **Create new solution**. Uncheck **Place solution and project in the same directory** if it's checked.
399399

400-
![The Create a new project dialog box with the Console App option highlighted.](media/mathclient-project-name-2019.png "Name the client project")
400+
![Screenshot of the Create a new project dialog box with the Console App option highlighted.](media/mathclient-project-name-2019.png "Name the client project")
401401

402402
1. Choose the **Create** button to create the client project.
403403

0 commit comments

Comments
 (0)