Skip to content

Commit 4a527b6

Browse files
author
mikeblome
committed
fixed new broken links
1 parent b6e98a6 commit 4a527b6

28 files changed

Lines changed: 55 additions & 58 deletions

‎docs/build/TOC.md‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -111,10 +111,10 @@
111111
### [Manifest Generation at the Command Line](manifest-generation-at-the-command-line.md)
112112
### [How to: Embed a Manifest Inside a C/C++ Application](how-to-embed-a-manifest-inside-a-c-cpp-application.md)
113113
## [Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies](troubleshooting-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
114-
# [Configure C++ projects for 64-bit, x64 targets](../configuring-programs-for-64-bit-visual-cpp.md)
115-
## [How to: Configure C++ Projects to Target 64-Bit, x64 Platforms](../how-to-configure-visual-cpp-projects-to-target-64-bit-platforms.md)
116-
## [How to: Enable a 64-Bit C++ Toolset on the Command Line](../how-to-enable-a-64-bit-visual-cpp-toolset-on-the-command-line.md)
117-
## [Common C++ 64-bit Migration Issues](../common-visual-cpp-64-bit-migration-issues.md)
114+
# [Configure C++ projects for 64-bit, x64 targets](configuring-programs-for-64-bit-visual-cpp.md)
115+
## [How to: Configure C++ Projects to Target 64-Bit, x64 Platforms](how-to-configure-visual-cpp-projects-to-target-64-bit-platforms.md)
116+
## [How to: Enable a 64-Bit C++ Toolset on the Command Line](how-to-enable-a-64-bit-visual-cpp-toolset-on-the-command-line.md)
117+
## [Common C++ 64-bit Migration Issues](common-visual-cpp-64-bit-migration-issues.md)
118118
## [x64 Software Conventions](x64-software-conventions.md)
119119
### [Overview of x64 Calling Conventions](overview-of-x64-calling-conventions.md)
120120
### [Types and Storage](types-and-storage.md)
@@ -156,11 +156,11 @@
156156
#### [Unwind Data Definitions in C](unwind-data-definitions-in-c.md)
157157
### [Intrinsics and Inline Assembly](intrinsics-and-inline-assembly.md)
158158
### [Image Format](image-format.md)
159-
# [Configure C++ for ARM processors](../configuring-programs-for-arm-processors-visual-cpp.md)
160-
## [Common C++ ARM Migration Issues](../common-visual-cpp-arm-migration-issues.md)
161-
## [Overview of ARM ABI Conventions](../overview-of-arm-abi-conventions.md)
162-
## [Overview of ARM64 ABI Conventions](../arm64-windows-abi-conventions.md)
163-
## [ARM Exception Handling](../arm-exception-handling.md)
164-
## [ARM64 Exception Handling](../arm64-exception-handling.md)
165-
# [Configuring Programs for Windows XP](../configuring-programs-for-windows-xp.md)
159+
# [Configure C++ for ARM processors](configuring-programs-for-arm-processors-visual-cpp.md)
160+
## [Common C++ ARM Migration Issues](common-visual-cpp-arm-migration-issues.md)
161+
## [Overview of ARM ABI Conventions](overview-of-arm-abi-conventions.md)
162+
## [Overview of ARM64 ABI Conventions](arm64-windows-abi-conventions.md)
163+
## [ARM Exception Handling](arm-exception-handling.md)
164+
## [ARM64 Exception Handling](arm64-exception-handling.md)
165+
# [Configuring Programs for Windows XP](configuring-programs-for-windows-xp.md)
166166
# [C/C++ Building Reference](reference/c-cpp-building-reference.md)

‎docs/build/creating-and-managing-visual-cpp-projects.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ To add third-party libraries, use the [vcpkg](../vcpkg.md) package manager. Run
3333

3434
## Set compiler options and other build properties
3535

36-
To configure build settings for a project, right-click on the project in **Solution Explorer** and choose **Properties**. For more information, see [Set compiler and build properties](working-with-project-properties).
36+
To configure build settings for a project, right-click on the project in **Solution Explorer** and choose **Properties**. For more information, see [Set compiler and build properties](working-with-project-properties.md).
3737

3838
## Compile and run
3939

@@ -47,7 +47,7 @@ In the Error List, you can press **F1** on a highlighted error to go to its docu
4747

4848
## In This Section
4949

50-
[Visual Studio C++ project templates](visual-cpp-project-types.md)<br>
50+
[Visual Studio C++ project templates](reference/visual-cpp-project-types.md)<br>
5151
Describes the MSBuild-based project types that are available for C++.
5252

5353
[File Types Created for C++ Projects](reference/file-types-created-for-visual-cpp-projects.md)<br>

‎docs/build/how-to-enable-a-64-bit-visual-cpp-toolset-on-the-command-line.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Visual C++ includes compilers, linkers, and other tools that you can use to crea
1313
>
1414
> For information about how to use the Visual Studio IDE to create 64-bit applications, see [How to: Configure Visual C++ Projects to Target 64-Bit, x64 Platforms](how-to-configure-visual-cpp-projects-to-target-64-bit-platforms.md).
1515
16-
When you install a C++ workload in the Visual Studio installer, it always installs 32-bit, x86-hosted, native and cross compiler tools to build x86 and x64 code. If you include the Universal Windows Platform workload, it also installs x86-hosted cross compiler tools to build ARM code. If you install these workloads on a 64-bit, x64 processor, you also get 64-bit native and cross compiler tools to build x86, x64, and ARM code. The 32-bit and 64-bit tools generate identical code, but the 64-bit tools support more memory for precompiled header symbols and the Whole Program Optimization ([/GL](reference/reference/gl-whole-program-optimization.md) and [/LTCG](reference/ltcg-link-time-code-generation.md)) options. If you run into memory limits when you use the 32-bit tools, try the 64-bit tools.
16+
When you install a C++ workload in the Visual Studio installer, it always installs 32-bit, x86-hosted, native and cross compiler tools to build x86 and x64 code. If you include the Universal Windows Platform workload, it also installs x86-hosted cross compiler tools to build ARM code. If you install these workloads on a 64-bit, x64 processor, you also get 64-bit native and cross compiler tools to build x86, x64, and ARM code. The 32-bit and 64-bit tools generate identical code, but the 64-bit tools support more memory for precompiled header symbols and the Whole Program Optimization ([/GL](reference/gl-whole-program-optimization.md) and [/LTCG](reference/ltcg-link-time-code-generation.md)) options. If you run into memory limits when you use the 32-bit tools, try the 64-bit tools.
1717

1818
## Use a 64-bit hosted developer command prompt shortcut
1919

‎docs/build/reference/c-cpp-build-tools.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Visual C++ provides the following command-line tools for viewing or manipulating
1717

1818
- [DUMPBIN.EXE](dumpbin-reference.md) displays information (such as a symbol table) about COFF binary files.
1919

20-
- [NMAKE](../../build/nmake-reference.md) reads and executes makefiles.
20+
- [NMAKE](nmake-reference.md) reads and executes makefiles.
2121

2222
- [ERRLOOK](value-edit-control.md), the Error Lookup utility, retrieves a system error message or module error message based on the value entered.
2323

‎docs/build/reference/command-modifiers.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,4 @@ You can specify one or more command modifiers preceding a command, optionally se
1616

1717
## See Also
1818

19-
[Commands in a Makefile](reference/commands-in-a-makefile.md)
19+
[Commands in a Makefile](commands-in-a-makefile.md)

‎docs/build/reference/compiler-options.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ To find a particular compiler option, see one of the following lists:
2929

3030
The topic for each compiler option discusses how it can be set in the development environment. For information on specifying options outside the development environment, see:
3131

32-
- [Compiler Command-Line Syntax](compiler-command-line-syntax.md)
32+
- [Compiler Command-Line Syntax](../compiler-command-line-syntax.md)
3333

3434
- [CL Command Files](../cl-command-files.md)
3535

@@ -42,6 +42,5 @@ The topic for each compiler option discusses how it can be set in the developmen
4242
## See also
4343

4444
[C/C++ Building Reference](c-cpp-building-reference.md)<br/>
45-
[Compiler Command Line Syntax](../compiler-command-line-syntax.md)<br/>
4645
[Fast Compilation](../fast-compilation.md)<br/>
4746
[CL Invokes the Linker](../cl-invokes-the-linker.md)

‎docs/build/reference/compiling-a-c-cpp-program.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ You can set compiler options for each project in its **Property Pages** dialog b
1616

1717
You can set compiler (CL.exe) options:
1818

19-
- [On the command line](compiler-command-line-syntax.md)
19+
- [On the command line](../compiler-command-line-syntax.md)
2020

2121
- [In command files](../cl-command-files.md)
2222

@@ -36,7 +36,7 @@ Compiler options are processed "left to right," and when a conflict is detected,
3636

3737
- [CL Invokes the Linker](../cl-invokes-the-linker.md)
3838

39-
For information on choosing the compiler host and target architecture, see [Configure Visual C++ for 64-bit, x64 targets](../../build/configuring-programs-for-64-bit-visual-cpp.md).
39+
For information on choosing the compiler host and target architecture, see [Configure Visual C++ for 64-bit, x64 targets](../configuring-programs-for-64-bit-visual-cpp.md).
4040

4141
## See Also
4242

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Precompiling requires planning, but it offers significantly faster compilations
3838

3939
Precompile code when you know that your source files use common sets of header files but don't include them in the same order, or when you want to include source code in your precompilation.
4040

41-
The precompiled-header options are [/Yc (Create Precompiled Header File)](../../build/reference/yc-create-precompiled-header-file.md) and [/Yu (Use Precompiled Header File)](../../build/reference/yu-use-precompiled-header-file.md). Use **/Yc** to create a precompiled header. When used with the optional [hdrstop](../../preprocessor/hdrstop.md) pragma, **/Yc** lets you precompile both header files and source code. Select **/Yu** to use an existing precompiled header in the existing compilation. You can also use **/Fp** with the **/Yc** and **/Yu** options to provide an alternative name for the precompiled header.
41+
The precompiled-header options are [/Yc (Create Precompiled Header File)](yc-create-precompiled-header-file.md) and [/Yu (Use Precompiled Header File)](yu-use-precompiled-header-file.md). Use **/Yc** to create a precompiled header. When used with the optional [hdrstop](../../preprocessor/hdrstop.md) pragma, **/Yc** lets you precompile both header files and source code. Select **/Yu** to use an existing precompiled header in the existing compilation. You can also use **/Fp** with the **/Yc** and **/Yu** options to provide an alternative name for the precompiled header.
4242

4343
The compiler option reference topics for **/Yu** and **/Yc** discuss how to access this functionality in the development environment.
4444

@@ -48,7 +48,7 @@ Because PCH files contain information about the machine environment as well as m
4848

4949
## Consistency Rules for Per-File Use of Precompiled Headers
5050

51-
The [/Yu](../../build/reference/yu-use-precompiled-header-file.md) compiler option lets you specify which PCH file to use.
51+
The [/Yu](yu-use-precompiled-header-file.md) compiler option lets you specify which PCH file to use.
5252

5353
When you use a PCH file, the compiler assumes the same compilation environment — one that uses consistent compiler options, pragmas, and so on — that was in effect when you created the PCH file, unless you specify otherwise. If the compiler detects an inconsistency, it issues a warning and identifies the inconsistency where possible. Such warnings do not necessarily indicate a problem with the PCH file; they simply warn you of possible conflicts. Consistency requirements for PCH files are described in the following sections.
5454

@@ -130,7 +130,7 @@ The code base of a software project is usually contained in multiple C or C++ so
130130

131131
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.
132132

133-
![Structure of a makefile that uses a precompiled header file](../../build/reference/media/vc30ow1.gif "Structure of a makefile that uses a precompiled header file") <br/>
133+
![Structure of a makefile that uses a precompiled header file](media/vc30ow1.gif "Structure of a makefile that uses a precompiled header file") <br/>
134134
Structure of a Makefile That Uses a Precompiled Header File
135135

136136
Beginning at the top of the diagram, both STABLEHDRS and BOUNDRY are NMAKE macros in which you list files not likely to need recompilation. These files are compiled by the command string
@@ -210,7 +210,7 @@ NMAKE
210210
NMAKE DEBUG=0
211211
```
212212

213-
For more information on makefiles, see [NMAKE Reference](../../build/nmake-reference.md). Also see [Compiler Options](../../build/reference/compiler-options.md) and the [Linker Options](../../build/reference/linker-options.md).
213+
For more information on makefiles, see [NMAKE Reference](nmake-reference.md). Also see [Compiler Options](compiler-options.md) and the [Linker Options](linker-options.md).
214214

215215
## Example Code for PCH
216216

@@ -298,5 +298,5 @@ int main( void )
298298

299299
## See Also
300300

301-
[C/C++ Building Reference](../../build/c-cpp-building-reference.md)<br/>
302-
[Compiler Options](../../build/reference/compiler-options.md)
301+
[C/C++ Building Reference](c-cpp-building-reference.md)<br/>
302+
[Compiler Options](compiler-options.md)

‎docs/build/reference/entry-entry-point-symbol.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The functions `main`, `WinMain`, and `DllMain` are the three forms of the user-d
3636

3737
When creating a managed image, the function specified to /ENTRY must have a signature of (LPVOID *var1*, DWORD *var2*, LPVOID *var3*).
3838

39-
For information on how to define your own `DllMain` entry point, see [DLLs and Visual C++ run-time library behavior](../../build/run-time-library-behavior.md) .
39+
For information on how to define your own `DllMain` entry point, see [DLLs and Visual C++ run-time library behavior](../run-time-library-behavior.md) .
4040

4141
### To set this linker option in the Visual Studio development environment
4242

‎docs/build/reference/favor-optimize-for-architecture-specifics.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ ms.assetid: ad264df2-e30f-4d68-8bd0-10d6bee71a2a
3232
> [!NOTE]
3333
> Intel64 architecture was previously known as Extended Memory 64 Technology, and the corresponding compiler option was **/favor:EM64T**.
3434
35-
For information about how to program for the x64 architecture, see [x64 Software Conventions](../../build/x64-software-conventions.md).
35+
For information about how to program for the x64 architecture, see [x64 Software Conventions](../x64-software-conventions.md).
3636

3737
### To set this compiler option in the Visual Studio development environment
3838

0 commit comments

Comments
 (0)