Skip to content

Commit 9254cab

Browse files
Merge pull request #5300 from MicrosoftDocs/main638805078605220832sync_temp
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
2 parents 799d0fc + 064fcb4 commit 9254cab

File tree

2 files changed

+3
-7
lines changed

2 files changed

+3
-7
lines changed

docs/build/how-to-modify-the-target-framework-and-platform-toolset.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Visual Studio also supports multitargeting for C++ projects. You can use the lat
2323

2424
## Target framework (C++/CLI project only)
2525

26-
When you change the target Framework, also change the platform toolset to a version that supports that Framework. For example, to target the .NET Framework 4.5, you must use a compatible platform toolset. These toolsets include Visual Studio 2015 (v140), Visual Studio 2013 (v120), or Visual Studio 2012 (v110). You can use the [Windows 7.1 SDK](https://www.microsoft.com/download/details.aspx?id=8279) to target .NET Framework 2.0, 3.0, 3.5, and 4.
26+
When you change the target Framework, also change the platform toolset to a version that supports that Framework. For example, to target the .NET Framework 4.5, you must use a compatible platform toolset. These toolsets include Visual Studio 2015 (v140), Visual Studio 2013 (v120), or Visual Studio 2012 (v110). You can use the [Windows 7.1 SDK](https://www.microsoft.com/en-us/download/details.aspx?id=8442) to target .NET Framework 2.0, 3.0, 3.5, and 4.
2727

2828
You can extend the target platform further by creating a custom platform toolset. For more information, see [C++ Native Multi-Targeting](https://devblogs.microsoft.com/cppblog/c-native-multi-targeting/) on the Visual C++ blog.
2929

docs/build/reference/nodefaultlib-ignore-libraries.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,13 @@
11
---
22
description: "Learn more about: /NODEFAULTLIB (Ignore libraries)"
33
title: "/NODEFAULTLIB (Ignore libraries)"
4-
ms.date: 09/09/2022
4+
ms.date: 04/16/2025
55
f1_keywords: ["VC.Project.VCLinkerTool.IgnoreAllDefaultLibraries", "VC.Project.VCLinkerTool.IgnoreDefaultLibraryNames", "VC.Project.VCLinkerTool.OVERWRITEAllDefaultLibraries", "VC.Project.VCLinkerTool.OVERWRITEDefaultLibraryNames", "/nodefaultlib"]
66
helpviewer_keywords: ["default libraries, removing", "-NODEFAULTLIB linker option", "libraries, ignore", "NODEFAULTLIB linker option", "/NODEFAULTLIB linker option", "ignore libraries linker option"]
7-
ms.assetid: 7270b673-6711-468e-97a7-c2925ac2be6e
87
---
98
# `/NODEFAULTLIB` (Ignore Libraries)
109

11-
The **`/NODEFAULTLIB`** linker option tells the linker to remove one or more default libraries from the list of libraries it searches when it resolves external references.
10+
Unless an optional library name is provided, the `/NODEFAULTLIB` linker option removes all libraries not explicitly specified on the linker command-line. This also includes `#pragma`, `cl.exe` command-line switches, libs referenced by other libs, and so on.
1211

1312
## Syntax
1413

@@ -34,11 +33,8 @@ If you use **`/NODEFAULTLIB`** to build your program without the C run-time libr
3433
### To set this linker option in the Visual Studio development environment
3534

3635
1. Open the project's **Property Pages** dialog box. For more information, see [Set compiler and build properties](../working-with-project-properties.md).
37-
3836
1. Select the **Configuration Properties** > **Linker** > **Input** property page.
39-
4037
1. Modify the **Ignore All Default Libraries** property. Or, specify a semicolon-separated list of the libraries you want to ignore in the **Ignore Specific Default Libraries** property. The **Linker** > **Command Line** property page shows the effect of the changes you make to these properties.
41-
4238
1. Choose **OK** or **Apply** to save your changes.
4339

4440
### To set this linker option programmatically

0 commit comments

Comments
 (0)