|
109 | 109 | <application>Visual Studio Command Prompt</application>.
|
110 | 110 | If you wish to build a 64-bit version, you must use the 64-bit version of
|
111 | 111 | the command, and vice versa.
|
112 |
| - In the <productname>Microsoft Windows SDK</productname>, start the |
113 |
| - <application>CMD shell</application> listed under the SDK on the Start Menu. |
114 |
| - In recent SDK versions you can change the targeted CPU architecture, build |
115 |
| - type, and target OS by using the <command>setenv</command> command, e.g. |
116 |
| - <command>setenv /x86 /release /xp</command> to target Windows XP or later |
117 |
| - with a 32-bit release build. See <command>/?</command> for other options to |
118 |
| - <command>setenv</command>. All commands should be run from the |
119 |
| - <filename>src\tools\msvc</filename> directory. |
| 112 | + Starting with <productname>Visual Studio 2017</productname> this can be |
| 113 | + done from the command line using <command>VsDevCmd.bat</command>, see |
| 114 | + <command>-help</command> for the available options and their default values. |
| 115 | + <command>vsvars32.bat</command> is available in |
| 116 | + <productname>Visual Studio 2015</productname> and earlier versions for the |
| 117 | + same purpose. |
| 118 | + From the <application>Visual Studio Command Prompt</application>, you can |
| 119 | + change the targeted CPU architecture, build type, and target OS by using the |
| 120 | + <command>vcvarsall.bat</command> command, e.g. |
| 121 | + <command>vcvarsall.bat x64 10.0.10240.0</command> to target Windows 10 |
| 122 | + with a 64-bit release build. See <command>-help</command> for the other |
| 123 | + options of <command>vcvarsall.bat</command>. All commands should be run from |
| 124 | + the <filename>src\tools\msvc</filename> directory. |
120 | 125 | </para>
|
121 | 126 |
|
122 | 127 | <para>
|
|
0 commit comments