Skip to content

Commit 9d1e743

Browse files
TylerMSFTTylerMSFT
TylerMSFT
authored and
TylerMSFT
committed
alt-text
1 parent a6eebef commit 9d1e743

3 files changed

Lines changed: 8 additions & 5 deletions

File tree

‎docs/build/creating-precompiled-header-files.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ The code base of a software project is often contained in multiple C or C++ sour
162162
The figure uses three diagrammatic devices to show the flow of the build process. Named rectangles represent each file or macro; the three macros represent one or more files. Shaded areas represent each compile or link action. Arrows show which files and macros are combined during the compilation or linking process.
163163

164164
![ The diagram is described in the text following the diagram.]()\
165-
Structure of a makefile that uses a precompiled header file
165+
Structure of a makefile that uses a precompiled header file:
166166

167167
:::image type="complex" source="media/vc30ow1.gif" alt-text="Diagram showing example inputs and outputs of a makefile that uses a precompiled header file.":::
168168
The diagram shows `$(STABLEHDRS)` and `$(BOUNDRY)` feeding into CL /c /W3 /Yc$(BOUNDRY) applib.cpp myapp.cpp. The output of that is $(STABLE.PCH). Then, applib.cpp and $(UNSTABLEHDRS) and $(STABLE.PCH) feed into CL /c /w3 /Yu $(BOUNDRY) applib.cpp, which produces applib.obj. myapp.cpp, $(UNSTABLEHDR), and $(STABLE.PCH) feed into CL /c /w3 /Yu $(BOUNDRY) myapp.cpp, which produces myapp.obj. Finally, applib.obj and myapp.obj are combined by LINK /NOD ONERROR:NOEXE $(OBJS), myapp, NUL, $(LIBS), NUL to produce myapp.exe.

‎docs/build/customize-cmake-settings.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -192,9 +192,9 @@ You can also directly edit *`CMakeSettings.json`* to create custom configuration
192192

193193
JSON IntelliSense helps you edit the *`CMakeSettings.json`* file:
194194

195-
:::image type="complex" source="media/cmake-json-intellisense.png" alt-text="Screenshot of the CMake JSON IntelliSense pop-up in the editor.":::
195+
:::image type="complex" source="media/cmake-json-intellisense.png" alt-text="Screenshot of the CMake JSON IntelliSense pop-up in the editor.":::
196196
The JSON IntelliSense pop-up for "configurations" shows buildCommandArgs, buildRoot, cmakeCommandArgs, configurationType, among several others.
197-
:::image-end:::
197+
:::image-end:::
198198

199199
For more information about each of the properties in the file, see [`CMakeSettings.json` schema reference](cmakesettings-reference.md).
200200

‎docs/windows/binary-editor.md‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,11 @@ The **Binary Editor** allows you to edit any resource at the binary level in eit
1717

1818
- To open the **Binary Editor** on an existing file, go to menu **File** > **Open** > **File**, select the file you want to edit, then select the drop arrow next to the **Open** button, and choose **Open With** > **Binary Editor**.
1919

20-
![Binary Editor.](../mfc/media/vcbinaryeditor2.gif "vcBinaryEditor2")<br/>
21-
Binary data for a dialog box displayed in the **Binary Editor**
20+
:::image type="complex" source="../mfc/media/vcbinaryeditor2.gif" alt-text="Screenshot of the Binary Editor.":::
21+
The binary editor is open on a file called Scribble.rc. mydata.rc. The file is split into three sections. The left section shows the address from the start of the file. The middle section shows columns of hexadecimal values from the file. The right section shows the ASCII characters that correspond to the hexadecimal values.
22+
:::image-end:::
23+
24+
Binary data for a dialog box displayed in the **Binary Editor**
2225

2326
Only certain ASCII values are represented in the **Binary Editor** (0x20 through 0x7E). Extended characters are displayed as periods in the right panel ASCII value section of the **Binary Editor**. The printable characters are ASCII values 32 through 126.
2427

0 commit comments

Comments
 (0)