Skip to content

Commit 0de9fdf

Browse files
TylerMSFTTylerMSFT
authored andcommitted
draft
1 parent 9d00f03 commit 0de9fdf

File tree

2 files changed

+5
-8
lines changed

2 files changed

+5
-8
lines changed

docs/build/reference/ifc-map.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -76,17 +76,14 @@ When `[[header-unit]]` is specified in the TOML, the compiler implicitly enables
7676

7777
### To set this compiler option in the Visual Studio development environment
7878

79-
1. To apply the **`/ifcMap`** option in the IDE, select the file in **Solution Explorer**. Right-click to open the context menu and select **Properties** to open the **Property Pages** dialog.
79+
1. Open the **Property Pages** dialog box for the project. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
8080

81-
1. Set the **Configuration** dropdown to **All Configurations**. Set the **Platform** dropdown to **All Platforms**.
81+
1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
8282

83-
1. Open the **Configuration Properties** > **C/C++** > **Output Files** property page.
84-
85-
1. Use the dropdown control to modify the **Module Output File Name** property to a directory name (ending in `\`) or an alternate file name. Or you can specify a directory + file name, for example, `c:\example\mymodule.ifc`. Choose **OK** or **Apply** to save your changes.
86-
87-
Alternatively, you can specify the `/ifcMap` switch with a right-click on the project name in the **Solution Explorer** > **Configuration Properties** > **C/C++** > **Command Line**.
83+
1. In the **Additional options** box, add `/ifcMap tomlfile.toml`.
8884

8985
## See also
9086

9187
[Overview of modules in C++](../../cpp/modules-cpp.md)\
88+
[Walkthrough: Build and import header units in Visual C++ projects](../../cpp/build/walkthrough-build-and-import-header-units-in-visual-cpp-projects.md)\
9289
[Using C++ Modules in MSVC from the Command Line](https://devblogs.microsoft.com/cppblog/using-cpp-modules-in-msvc-from-the-command-line-part-1/)

docs/cpp/modules-cpp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ import std.regex;
4545

4646
To consume the Microsoft Standard Library modules, compile your program with [`/EHsc`](../build/reference/eh-exception-handling-model.md) and [`/MD`](../build/reference/md-mt-ld-use-run-time-library.md) options.
4747

48-
## Basic example
48+
## Example
4949

5050
The following example shows a simple module definition in a source file called *`Example.ixx`*. The *`.ixx`* extension is required for module interface files in Visual Studio. In this example, the interface file contains both the function definition and the declaration. However, you can also place the definitions in one or more separate module implementation files, as shown in a later example. The `export module Example;` statement indicates that this file is the primary interface for a module called `Example`. The **`export`** modifier on `f()` indicates that this function is visible when `Example` is imported by another program or module. The module references a namespace `Example_NS`.
5151

0 commit comments

Comments
 (0)