You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fe1e21d
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/build/reference/optimization-best-practices.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The **/Gy** switch is also very useful. It generates a separate COMDAT for each
26
26
27
27
For linking in 64-bit environments, it is recommended to use the **/OPT:REF,ICF** linker option, and in 32-bit environments, **/OPT:REF** is recommended. For more information, see [/OPT (Optimizations)](../../build/reference/opt-optimizations.md).
28
28
29
-
It is also strongly recommended to generate debug symbols, even with optimized release builds. It doesn’t effect the generated code, and it makes it a lot easier to debug your application, if need be.
29
+
It is also strongly recommended to generate debug symbols, even with optimized release builds. It doesn’t affect the generated code, and it makes it a lot easier to debug your application, if need be.
Specifies a SourceLink configuration file to include in the PDB file generated by the linker.
9
+
Specifies a Source Link configuration file to include in the PDB file generated by the linker.
10
10
11
11
## Syntax
12
12
@@ -19,7 +19,7 @@ Specifies a JSON-formatted configuration file that contains a simple mapping of
19
19
20
20
## Remarks
21
21
22
-
SourceLink is a language- and source-control agnostic system for providing source debugging for binaries. SourceLink is supported for native C++ binaries starting in Visual Studio 2017 version 15.8. For an overview of SourceLink, see [Source Link](https://github.com/dotnet/designs/blob/master/accepted/diagnostics/source-link.md). For information on how to use SourceLink in your projects and how to generate the SourceLink file as part of your project, see [Using SourceLink](https://github.com/dotnet/sourcelink#using-sourcelink).
22
+
Source Link is a language- and source-control agnostic system for providing source debugging for binaries. Source Link is supported for native C++ binaries starting in Visual Studio 2017 version 15.8. For an overview of Source Link, see [Source Link](https://github.com/dotnet/designs/blob/master/accepted/diagnostics/source-link.md). For information on how to use Source Link in your projects and how to generate the SourceLink file as part of your project, see [Using Source Link](https://github.com/dotnet/sourcelink#using-source-link-in-c-projects).
23
23
24
24
### To set the /SOURCELINK linker option in Visual Studio
Copy file name to clipboardExpand all lines: docs/linux/cmake-linux-project.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ When you install the Linux C++ workload for Visual Studio, CMake support for Lin
13
13
This topic assumes you have basic familiarity with CMake support in Visual Studio. For more information, see [CMake Tools for Visual C++](../ide/cmake-tools-for-visual-cpp.md). For more information about CMake itself, see [Build, Test and Package Your Software With CMake](https://cmake.org/).
14
14
15
15
> [!NOTE]
16
-
> The CMake support in Visual Studio requires the server mode support that was introduced in CMake 3.8. For a Microsoft-provided CMake variant download the latest prebuilt binaries at [https://github.com/Microsoft/CMake/releases](https://github.com/Microsoft/CMake/releases).
16
+
> The CMake support in Visual Studio requires the server mode support that was introduced in CMake 3.8. For a Microsoft-provided CMake variant download the latest prebuilt binaries at [https://github.com/Microsoft/CMake/releases](https://github.com/Microsoft/CMake/releases). In Visual Studio 2019 the prebuilt binaries can be automatically deployed (see [Download prebuilt CMake binaries](#download-prebuilt-cmake-binaries)).
17
17
18
18
## Open a folder
19
19
@@ -105,6 +105,9 @@ These options allow you to run commands on the remote box before and after build
105
105
106
106
Your Linux distro may have an older version of CMake. The CMake support in Visual Studio requires the server mode support that was introduced in CMake 3.8. For a Microsoft-provided CMake variant download the latest prebuilt binaries at [https://github.com/Microsoft/CMake/releases](https://github.com/Microsoft/CMake/releases).
107
107
108
+
**Visual Studio 2019**<br/>
109
+
If a valid CMake is not found on the remote machine an infobar will appear and provide an option to automatically deploy the prebuilt CMake binaries. The binaries will be installed to `~/.vs/cmake`. After deploying the binaries, your project will automatically regenerate. Note that if the CMake specified by the `cmakeExecutable` field in `CMakeSettings.json` is invalid (doesn't exist or is an unsupported version) and the prebuilt binaries are present Visual Studio will ignore `cmakeExecutable` and use the prebuilt binaries.
110
+
108
111
## See Also
109
112
110
113
[Working with Project Properties](../ide/working-with-project-properties.md)<br/>
To simplify the transporting of code for international use, the Microsoft run-time library provides Microsoft-specific generic-text mappings for many data types, routines, and other objects. You can use these mappings, which are defined in tchar.h, to write generic code that can be compiled for single-byte, multibyte, or Unicode character sets, depending on a manifest constant that you define by using a `#define` statement. Generic-text mappings are Microsoft extensions that are not ANSI compatible.
11
11
12
-
By using the tchar.h, you can build single-byte, Multibyte Character Set (MBCS), and Unicode applications from the same sources. tchar.h defines macros (which have the prefix `_tcs`) that, with the correct preprocessor definitions, map to `str`, `_mbs`, or `wcs` functions, as appropriate. To build MBCS, define the symbol `_MBCS`. To build Unicode, define the symbol `_UNICODE`. To build a single-byte application, define neither (the default). By default, `_MBCS` is defined for MFC applications.
12
+
By using the tchar.h, you can build single-byte, Multibyte Character Set (MBCS), and Unicode applications from the same sources. tchar.h defines macros (which have the prefix `_tcs`) that, with the correct preprocessor definitions, map to `str`, `_mbs`, or `wcs` functions, as appropriate. To build MBCS, define the symbol `_MBCS`. To build Unicode, define the symbol `_UNICODE`. To build a single-byte application, define neither (the default). By default, `_UNICODE` is defined for MFC applications.
13
13
14
14
The `_TCHAR` data type is defined conditionally in tchar.h. If the symbol `_UNICODE` is defined for your build, `_TCHAR` is defined as **wchar_t**; otherwise, for single-byte and MBCS builds, it is defined as **char**. (**wchar_t**, the basic Unicode wide-character data type, is the 16-bit counterpart to an 8-bit signed **char**.) For international applications, use the `_tcs` family of functions, which operate in `_TCHAR` units, not bytes. For example, `_tcsncpy` copies `n``_TCHARs`, not `n` bytes.
Copy file name to clipboardExpand all lines: docs/visual-cpp-help-and-community.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Here's how to getting information about how to write C++ code and use the Visual
21
21
|Title|Description|
22
22
|-----------|-----------------|
23
23
|[Visual C++](visual-cpp-in-visual-studio.md)|Contains reference and conceptual documentation about Visual C++. Part of the MSDN Library.|
24
-
|[Windows Developer Center](https://developer.microsoft.com/windows/)|Contains information about how to use C++ and other languages to develop apps for Windows 8. Part of the Windows Developer Center; the C++ content is under the Docs > Language Reference node.|
24
+
|[Windows Developer Center](https://developer.microsoft.com/windows/)|Contains information about how to use C++ and other languages to develop apps for Windows 10. Part of the Windows Developer Center; the C++ content is under the Docs > Language Reference node.|
25
25
26
26
### Online and Offline Documentation
27
27
@@ -38,4 +38,4 @@ Many sections of the documentation are also available in PDF form. These section
38
38
|[Visual C++ Team Blog](https://blogs.msdn.microsoft.com/vcblog/)|Contains posts on various subjects by the experts on the Visual C++ product team.|
39
39
|[Channel 9](https://channel9.msdn.com/)|Contains video interviews and lectures. Use the search box on the Channel 9 home page to find C++ content.|
40
40
|[Visual Studio](https://visualstudio.microsoft.com/)|Contains articles and news about Visual Studio and related development tools.|
41
-
|[MSDN forums](https://social.msdn.microsoft.com/Forums/home?category=visualc) and [Developer Community](https://developercommunity.visualstudio.com)|Official Microsoft forums where you can post questions about C++ and get answers from Microsoft and from experts in the community.|
41
+
|[MSDN forums](https://social.msdn.microsoft.com/Forums/home?category=visualc) and [Developer Community](https://developercommunity.visualstudio.com)|Official Microsoft forums where you can post questions about C++ and get answers from Microsoft and from experts in the community.|
0 commit comments