Skip to content

Commit 7efbd80

Browse files
author
mikeblome
committed
misc fixes to titles, redirects and link text
1 parent 40ef717 commit 7efbd80

31 files changed

+84
-100
lines changed

‎.openpublishing.redirection.json‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -115,6 +115,11 @@
115115
"redirect_url": "/cpp/build/reference/linking",
116116
"redirect_document_id": false
117117
},
118+
{
119+
"source_path": "docs/build/reference/setting-linker-options.md",
120+
"redirect_url": "/cpp/build/reference/linking",
121+
"redirect_document_id": false
122+
},
118123
{
119124
"source_path": "docs/build/reference/link-environment-variables.md",
120125
"redirect_url": "/cpp/build/reference/linking",
@@ -140,6 +145,11 @@
140145
"redirect_url": "/cpp/build/linking-an-executable-to-a-dll#determining-which-linking-method-to-use",
141146
"redirect_document_id": false
142147
},
148+
{
149+
"source_path": "docs/build/creating-desktop-projects-by-using-application-wizards.md",
150+
"redirect_url": "/cpp/build/creating-and-managing-visual-cpp-projects",
151+
"redirect_document_id": false
152+
},
143153
{
144154
"source_path": "docs/build/differences-between-applications-and-dlls.md",
145155
"redirect_url": "/cpp/build/dlls-in-visual-cpp#differences-between-applications-and-dlls",
@@ -449,6 +459,21 @@
449459
"source_path": "docs/c-runtime-library/size-specification.md",
450460
"redirect_url": "/cpp/c-runtime-library/format-specification-syntax-printf-and-wprintf-functions#size",
451461
"redirect_document_id": false
462+
},
463+
{
464+
"source_path": "docs/ide/how-to-enable-intellisense-for-makefile-projects.md",
465+
"redirect_url": "/cpp/build/reference/creating-a-makefile-project",
466+
"redirect_document_id": false
467+
},
468+
{
469+
"source_path": "docs/ide/makefile-project-wizard.md",
470+
"redirect_url": "/cpp/build/reference/creating-a-makefile-project",
471+
"redirect_document_id": false
472+
},
473+
{
474+
"source_path": "docs/ide/application-settings-makefile-project-wizard.md",
475+
"redirect_url": "/cpp/build/reference/creating-a-makefile-project",
476+
"redirect_document_id": false
452477
},
453478
{
454479
"source_path": "docs/ide/add-class-dialog-box.md",

‎docs/atl/reference/adding-a-new-interface-in-an-atl-project.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,6 @@ You can add a new interface to your control in one of two ways: manually or usin
3333

3434
[ATL Project Wizard](../../atl/reference/atl-project-wizard.md)<br/>
3535
[Visual C++ Project Types](../../build/reference/visual-cpp-project-types.md)<br/>
36-
[Creating Desktop Projects By Using Application Wizards](../../build/creating-desktop-projects-by-using-application-wizards.md)<br/>
3736
[Programming with ATL and C Run-Time Code](../../atl/programming-with-atl-and-c-run-time-code.md)<br/>
3837
[Fundamentals of ATL COM Objects](../../atl/fundamentals-of-atl-com-objects.md)<br/>
3938
[Default ATL Project Configurations](../../atl/reference/default-atl-project-configurations.md)

‎docs/atl/reference/adding-objects-and-controls-to-an-atl-project.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,6 @@ You can use one of the ATL code wizards to add an object or a control to your AT
3535

3636
[ATL Project Wizard](../../atl/reference/atl-project-wizard.md)<br/>
3737
[Visual C++ Project Types](../../build/reference/visual-cpp-project-types.md)<br/>
38-
[Creating Desktop Projects By Using Application Wizards](../../build/creating-desktop-projects-by-using-application-wizards.md)<br/>
3938
[Fundamentals of ATL COM Objects](../../atl/fundamentals-of-atl-com-objects.md)<br/>
4039
[Programming with ATL and C Run-Time Code](../../atl/programming-with-atl-and-c-run-time-code.md)<br/>
4140
[Default ATL Project Configurations](../../atl/reference/default-atl-project-configurations.md)

‎docs/atl/reference/atl-project-wizard.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,6 @@ You can specify project properties (for example, [whether to link statically to
4141

4242
[Creating and Managing Visual C++ Projects](../../build/creating-and-managing-visual-cpp-projects.md)<br/>
4343
[Visual C++ Project Types](../../build/reference/visual-cpp-project-types.md)<br/>
44-
[Creating Desktop Projects By Using Application Wizards](../../build/creating-desktop-projects-by-using-application-wizards.md)<br/>
4544
[Fundamentals of ATL COM Objects](../../atl/fundamentals-of-atl-com-objects.md)<br/>
4645
[Programming with ATL and C Run-Time Code](../../atl/programming-with-atl-and-c-run-time-code.md)<br/>
4746
[Tutorial](../../atl/active-template-library-atl-tutorial.md)

‎docs/atl/reference/making-an-atl-object-noncreatable.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,6 @@ You can change the attributes of an ATL-based COM object so that a client cannot
2929
3030
[ATL Project Wizard](../../atl/reference/atl-project-wizard.md)<br/>
3131
[Visual C++ Project Types](../../build/reference/visual-cpp-project-types.md)<br/>
32-
[Creating Desktop Projects By Using Application Wizards](../../build/creating-desktop-projects-by-using-application-wizards.md)<br/>
3332
[Programming with ATL and C Run-Time Code](../../atl/programming-with-atl-and-c-run-time-code.md)<br/>
3433
[Fundamentals of ATL COM Objects](../../atl/fundamentals-of-atl-com-objects.md)<br/>
3534
[Default ATL Project Configurations](../../atl/reference/default-atl-project-configurations.md)

‎docs/atl/reference/specifying-compiler-optimization-for-an-atl-project.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,6 @@ in stdafx.h, before all other ATL header files are included.
4444

4545
[ATL Project Wizard](../../atl/reference/atl-project-wizard.md)<br/>
4646
[Visual C++ Project Types](../../build/reference/visual-cpp-project-types.md)<br/>
47-
[Creating Desktop Projects By Using Application Wizards](../../build/creating-desktop-projects-by-using-application-wizards.md)<br/>
4847
[Programming with ATL and C Run-Time Code](../../atl/programming-with-atl-and-c-run-time-code.md)<br/>
4948
[Fundamentals of ATL COM Objects](../../atl/fundamentals-of-atl-com-objects.md)<br/>
5049
[novtable](../../cpp/novtable.md)<br/>

‎docs/build/TOC.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,7 @@
1818
### [Specify Release Configuration Settings, Create New Project From Existing Code Files Wizard](specify-release-configuration.md)
1919
# [CMake projects](cmake-tools-for-visual-cpp.md)
2020
# [Open Folder projects](non-msbuild-projects.md)
21-
# [Windows makefile projects (NMAKE)](creating-a-makefile-project.md)
22-
# [Create optimized release builds](release-builds.md)
21+
# [C++ release builds](release-builds.md)
2322
## [How to: Create a Release Build](how-to-create-a-release-build.md)
2423
## [Common Problems When Creating a Release Build](common-problems-when-creating-a-release-build.md)
2524
## [Fixing Release Build Problems](fixing-release-build-problems.md)

‎docs/build/building-c-cpp-programs.md‎

Lines changed: 15 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -6,44 +6,46 @@ f1_keywords: ["vcbuilding", "buildingaprogramVC"]
66
helpviewer_keywords: ["builds [C++]", "Visual C++ projects, building", "projects [C++], building", "builds [C++], options", "Visual C++, build options"]
77
ms.assetid: fa6ed4ff-334a-4d99-b5e2-a1f83d2b3008
88
---
9-
# Building C/C++ projects
9+
# Building C/C++ projects in Visual Studio
1010

11-
You can use Visual Studio 2017 to edit, compile and build any C++ code base with full IntelliSense support without having to convert that code into a Visual Studio project or use MSVC to compile it. For example, you can edit a CMake project in Visual Studio on your local machine, then compile it using g++ on a remote Linux machine.
11+
You can use Visual Studio 2017 to edit, compile and build any C++ code base with full IntelliSense support without having to convert that code into a Visual Studio project or compile with the MSVC toolset. For example, you can edit a cross-platform CMake project in Visual Studio on a Windows machine, then compile it for Linux using g++ on a remote Linux machine.
1212

1313
## C++ compilation
1414

1515
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-load library (.dll) or a static library (.lib).
1616

17-
Basic compilation involves three main steps:
17+
Basic C++ compilation involves three main steps:
1818

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

2323
## The MSVC toolset
2424

25-
You can build simple programs by invoking the MSVC compiler (cl.exe) directly from the command line. The following example is taken from [](). The command accepts a single source code file, and builds an executable called *hello.exe*:
25+
The Microsoft C++ compiler, linker, standard libraries, and related utilities comprise the MSCV compiler toolset (also called a toolchain or "build tools"). These are included in Visual Studio. You can also download and use the toolset as a standalone package for free from the [Build Tools for Visual Studio 2017 download location](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2017).
26+
27+
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*:
2628

2729
```cmd
2830
cl /EHsc hello.cpp
2931
```
30-
Note that here the compiler (cl.exe) automatically invokes the C++ preprocessor and the linker to produce the final output file.
31-
32-
The MSVC compiler, linker, C++ standard libraries, and related utilities comprise the MSCV toolset. You can download and use the toolset as a standalone package for free from the [MSVC compiler tools download location](). For more information, see [Building on the command line](building-on-the-command-line.md).
32+
Note that 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).
3333

3434
## Build systems and projects
3535

3636
Most real-world programs use some kind of *build system* to manage complexities of compiling multiple source files for multiple configurations (i.e. 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*.
3737

3838
The following list shows various options for building C++ projects in Visual Studio:
3939

40-
- 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).
40+
- 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.
4141

42-
- 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 []().
42+
- 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-tools-for-visual-cpp.md).
4343

44-
- 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 []().
44+
- 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](non-msbuild-projects.md).
4545

46-
- open a folder that contains a makefile, or any other build system configuration file. You can configure Visual Studio to invoke any arbitrary build commands by adding JSON files to the folder. Or you can simply use the command line to build. For more information, see []().
46+
- open a folder that contains a makefile, or any other build system configuration file. You can configure Visual Studio to invoke any arbitrary build commands by adding JSON files to the folder. For more information, see [Open Folder projects](non-msbuild-projects.md).
47+
48+
- Open a Windows makefile in Visual Studio. For more information, see [NMAKE Reference](reference/nmake-reference.md).
4749

4850
## MSBuild from the command line
4951

@@ -60,9 +62,6 @@ How to code, build, and deploy CMake projects in Visual Studio.
6062
[Open Folder projects](non-msbuild-projects.md)
6163
How to use Visual Studio to code, build and deploy C++ projects based on any arbitrary build system, or no build system. at all.
6264

63-
[Windows makefile projects (NMAKE)](creating-a-makefile-project.md)
64-
How to use [NMAKE](reference/nmake-reference.md) to build makefile projects on Windows.
65-
6665
[Release builds](release-builds.md)
6766
How to create and troubleshoot optimized release builds for deployment to end users.
6867

0 commit comments

Comments
 (0)