Skip to content

Commit 439ffbd

Browse files
authored
Add backticks in "C/C++ projects and build systems in Visual Studio" topic
1 parent c487684 commit 439ffbd

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

docs/build/projects-and-build-systems-cpp.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,25 +13,25 @@ You can use Visual Studio to edit, compile, and build any C++ code base with ful
1313

1414
## C++ compilation
1515

16-
To *build* a C++ program means to compile source code from one or more files and then link those files into an executable file (.exe), a dynamic-link library (.dll) or a static library (.lib).
16+
To *build* a C++ program means to compile source code from one or more files and then link those files into an executable file (`.exe`), a dynamic-link library (`.dll`) or a static library (`.lib`).
1717

1818
Basic C++ compilation involves three main steps:
1919

2020
- The C++ preprocessor transforms all the #directives and macro definitions in each source file. This creates a *translation unit*.
21-
- The C++ compiler compiles each translation unit into object files (.obj), applying whatever compiler options have been set.
21+
- The C++ compiler compiles each translation unit into object files (`.obj`), applying whatever compiler options have been set.
2222
- The *linker* merges the object files into a single executable, applying the linker options that have been set.
2323

2424
## The MSVC toolset
2525

2626
The Microsoft C++ compiler, linker, standard libraries, and related utilities make up the MSVC compiler toolset (also called a toolchain or "build tools"). These are included in Visual Studio. You can also download and use the command-line toolset as a free standalone package. For more information, see [Build Tools for Visual Studio](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022) on the Visual Studio Downloads page.
2727

28-
You can build simple programs by invoking the MSVC compiler (cl.exe) directly from the command line. The following command accepts a single source code file, and invokes cl.exe to build an executable called *hello.exe*:
28+
You can build simple programs by invoking the MSVC compiler (`cl.exe`) directly from the command line. The following command accepts a single source code file, and invokes `cl.exe` to build an executable called *`hello.exe`*:
2929

3030
```cmd
3131
cl /EHsc hello.cpp
3232
```
3333

34-
Here the compiler (cl.exe) automatically invokes the C++ preprocessor and the linker to produce the final output file. For more information, see [Building on the command line](building-on-the-command-line.md).
34+
Here the compiler (`cl.exe`) automatically invokes the C++ preprocessor and the linker to produce the final output file. For more information, see [Building on the command line](building-on-the-command-line.md).
3535

3636
## Build systems and projects
3737

@@ -41,7 +41,7 @@ The following list shows various options for Visual Studio Projects - C++:
4141

4242
- Create a Visual Studio project by using the Visual Studio IDE and configure it by using property pages. Visual Studio projects produce programs that run on Windows. For an overview, see [Compiling and Building](/visualstudio/ide/compiling-and-building-in-visual-studio) in the Visual Studio documentation.
4343

44-
- Open a folder that contains a CMakeLists.txt file. CMake support is integrated into Visual Studio. You can use the IDE to edit, test, and debug without modifying the CMake files in any way. This enables you to work in the same CMake project as others who might be using different editors. CMake is the recommended approach for cross-platform development. For more information, see [CMake projects](cmake-projects-in-visual-studio.md).
44+
- Open a folder that contains a `CMakeLists.txt` file. CMake support is integrated into Visual Studio. You can use the IDE to edit, test, and debug without modifying the CMake files in any way. This enables you to work in the same CMake project as others who might be using different editors. CMake is the recommended approach for cross-platform development. For more information, see [CMake projects](cmake-projects-in-visual-studio.md).
4545

4646
- Open a loose folder of source files with no project file. Visual Studio will use heuristics to build the files. This is an easy way to compile and run small console applications. For more information, see [Open Folder projects](open-folder-projects-cpp.md).
4747

@@ -51,7 +51,7 @@ The following list shows various options for Visual Studio Projects - C++:
5151

5252
## MSBuild from the command line
5353

54-
You can invoke MSBuild from the command line by passing it a .vcxproj file along with command-line options. This approach requires a good understanding of MSBuild, and is recommended only when necessary. For more information, see [MSBuild](msbuild-visual-cpp.md).
54+
You can invoke MSBuild from the command line by passing it a `.vcxproj` file along with command-line options. This approach requires a good understanding of MSBuild, and is recommended only when necessary. For more information, see [MSBuild](msbuild-visual-cpp.md).
5555

5656
## In This Section
5757

@@ -74,7 +74,7 @@ Discusses how to use the C/C++ compiler and build tools directly from the comman
7474
How to create, debug, and deploy C/C++ DLLs (shared libraries) in Visual Studio.
7575

7676
[Walkthrough: Creating and Using a Static Library](walkthrough-creating-and-using-a-static-library-cpp.md)\
77-
How to create a **.lib** binary file.
77+
How to create a `.lib` binary file.
7878

7979
[Building C/C++ Isolated Applications and Side-by-side Assemblies](building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)\
8080
Describes the deployment model for Windows Desktop applications, based on the idea of isolated applications and side-by-side assemblies.

0 commit comments

Comments
 (0)