Skip to content

Commit 5314a60

Browse files
Merge pull request #6227 from MicrosoftDocs/main
Auto Publish – main to live - 2026-01-26 18:30 UTC
2 parents 621f2bf + 56ec8fb commit 5314a60

4 files changed

Lines changed: 9 additions & 3 deletions

File tree

docs/build/reference/creating-a-makefile-project.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,13 @@ The output file that you specify in the project has no effect on the name that t
3030

3131
### To create a makefile project in Visual Studio
3232

33-
1. From the Visual Studio main menu, choose **File** > **New** > **Project** and type "makefile" into the search box. If you see more than one project template, select from the options depending on your target platform.
33+
1. From the Visual Studio main menu, choose **File** > **New** > **Project/Solution**.
34+
35+
:::image type="content" source="media/file-new-project.png" alt-text="Screenshot of the File > New > Project/Solution menu item.":::
36+
37+
1. Type *makefile* into the search box. If you see more than one project template, select the option for your target platform.
38+
39+
:::image type="content" source="media/create-project.png" alt-text="Screenshot of the Create a new project dialog. The Create a new project text field text box contains the text: makefile.":::
3440

3541
1. **Windows only**: In the Makefile project **Debug Configuration Settings** page, provide the command, output, clean, and rebuild information for debug and retail builds. Choose **Next** if you want to specify different settings for a Release configuration.
3642

28.2 KB
Loading
15.1 KB
Loading

docs/ide/include-cleanup-config.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Configure C/C++ Include Cleanup in Visual Studio"
33
description: "Learn how to configure C/C++ Include Cleanup."
4-
ms.date: 10/10/2023
4+
ms.date: 01/23/2026
55
ms.topic: "how-to"
66
f1_keywords: ["config include cleanup"]
77
helpviewer_keywords: ["config include cleanup"]
@@ -59,7 +59,7 @@ The `.editorconfig` settings that you can use with Include Cleanup are:
5959
| `cpp_include_cleanup_excluded_files`</br></br>Excludes the specified files from Include Cleanup messages. You won't get a suggestion related to the header at all, whether to add it or that it's unused. | *filename* | `cpp_include_cleanup_excluded_files = vcruntime.h, vcruntime_string.h` |
6060
| `cpp_include_cleanup_required_files`</br></br>Specify that usage of *file1* requires *file2*. For example, specify that if you use `atlwin.h` that `altbase.h` must also be included. | *file1*:*file2* | `cpp_include_cleanup_required_files = atlwin.h:altbase.h, atlcom.h:altbase.h` |
6161
| `cpp_include_cleanup_replacement_files`</br></br>Replaces *file1* with *file2* during Include Cleanup processing. For example, you may prefer using `cstdio` over `stdio.h`. If you have a file with both `#include <cstdio>` and `#include <stdio.h>` and you consume content only from `stdio.h`, with this setting Include Cleanup will tell you to remove `stdio.h` because it replaced the usage of `cstdio` with `stdio.h` during processing. If you don't use the contents from either, Include Cleanup will tell you to remove both.| *file1*:*file2* | `cpp_include_cleanup_replacement_files = stdio.h:cstdio,stdint.h:cstdint` |
62-
| `cpp_include_cleanup_alternate_files`</br></br>Don't generate a message for indirect include *file2* if *file1* is included. For example, if you `#include <windows.h>` and are only using something from its indirectly included header `winerror.h`, Include Cleanup won't prompt to add `winerror.h`. Useful when you prefer to include a facade header file instead of the indirect includes it contains. | *file1*:*file2* | `cpp_include_cleanup_alternate_files = windows.h:winerror.h, windows.h:minwindef.h` |
62+
| `cpp_include_cleanup_alternate_files`</br></br>Suppress messages for indirect includes. For example, if you `#include <windows.h>` and only use content from its indirectly included headers `winerror.h` or `minwindef.h`, the tool won't suggest adding them. | *file1*:*file2*[:*file3*...][,*file4*:*file5*...] | `cpp_include_cleanup_alternate_files = windows.h:winerror.h:minwindef.h`</br>or</br>`cpp_include_cleanup_alternate_files = windows.h:winerror.h:minwindef.h,umbrella.h:internal.h`|
6363

6464
## See also
6565

0 commit comments

Comments
 (0)