From 135a0e72ec55e1db47507eebee3688c881ee20e8 Mon Sep 17 00:00:00 2001 From: Kishkin Date: Tue, 13 Apr 2021 17:35:52 +0530 Subject: [PATCH 1/3] fixed issue #2169 --- docs/build/projects-and-build-systems-cpp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/build/projects-and-build-systems-cpp.md b/docs/build/projects-and-build-systems-cpp.md index fd077fb4bb0..bd3dbf5d595 100644 --- a/docs/build/projects-and-build-systems-cpp.md +++ b/docs/build/projects-and-build-systems-cpp.md @@ -32,7 +32,7 @@ cl /EHsc hello.cpp 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). -## Build systems and projects +## invoke Most real-world programs use some kind of *build system* to manage complexities of compiling multiple source files for multiple configurations (debug vs. release), multiple platforms (x86, x64, ARM, and so on), custom build steps, and even multiple executables that must be compiled in a certain order. You make settings in a build configuration file(s), and the build system accepts that file as input before it invoke the compiler. The set of source code files and build configuration files needed to build an executable file is called a *project*. From b3e57cf6ddec3d9c7d041eadf2162fd4509c208a Mon Sep 17 00:00:00 2001 From: Kishkin Date: Tue, 13 Apr 2021 18:07:52 +0530 Subject: [PATCH 2/3] Fixed issue #2169 --- docs/build/projects-and-build-systems-cpp.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/build/projects-and-build-systems-cpp.md b/docs/build/projects-and-build-systems-cpp.md index bd3dbf5d595..30ea27ac3a0 100644 --- a/docs/build/projects-and-build-systems-cpp.md +++ b/docs/build/projects-and-build-systems-cpp.md @@ -32,9 +32,9 @@ cl /EHsc hello.cpp 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). -## invoke +## Build Systems and Projects -Most real-world programs use some kind of *build system* to manage complexities of compiling multiple source files for multiple configurations (debug vs. release), multiple platforms (x86, x64, ARM, and so on), custom build steps, and even multiple executables that must be compiled in a certain order. You make settings in a build configuration file(s), and the build system accepts that file as input before it invoke the compiler. The set of source code files and build configuration files needed to build an executable file is called a *project*. +Most real-world programs use some kind of *build system* to manage complexities of compiling multiple source files for multiple configurations (debug vs. release), multiple platforms (x86, x64, ARM, and so on), custom build steps, and even multiple executables that must be compiled in a certain order. You make settings in a build configuration file(s), and the build system accepts that file as input before it invokes the compiler. The set of source code files and build configuration files needed to build an executable file is called a *project*. The following list shows various options for Visual Studio Projects - C++: From 04e0eb35f58ee26b9e697336d73a1114ad107965 Mon Sep 17 00:00:00 2001 From: Colin Robertson Date: Tue, 13 Apr 2021 13:46:36 -0700 Subject: [PATCH 3/3] Update style Per style guidelines, use sentence case in headings. --- docs/build/projects-and-build-systems-cpp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/build/projects-and-build-systems-cpp.md b/docs/build/projects-and-build-systems-cpp.md index 30ea27ac3a0..ef71571b404 100644 --- a/docs/build/projects-and-build-systems-cpp.md +++ b/docs/build/projects-and-build-systems-cpp.md @@ -32,7 +32,7 @@ cl /EHsc hello.cpp 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). -## Build Systems and Projects +## Build systems and projects Most real-world programs use some kind of *build system* to manage complexities of compiling multiple source files for multiple configurations (debug vs. release), multiple platforms (x86, x64, ARM, and so on), custom build steps, and even multiple executables that must be compiled in a certain order. You make settings in a build configuration file(s), and the build system accepts that file as input before it invokes the compiler. The set of source code files and build configuration files needed to build an executable file is called a *project*.