|
9 | 9 | For an official release, the installer should be built with the |
10 | 10 | Tools/msi/buildrelease.bat script and environment variables: |
11 | 11 |
|
12 | | - set PYTHON=<path to Python 2.7> |
| 12 | + set PYTHON=<path to Python 2.7 or 3.4> |
13 | 13 | set SPHINXBUILD=<path to sphinx-build.exe> |
14 | 14 | set PATH=<path to Mercurial (hg.exe)>; |
15 | 15 | <path to HTML Help Compiler (hhc.exe)>;%PATH% |
@@ -87,7 +87,7 @@ and extracted to the externals/ directory. |
87 | 87 | For an official release, the installer should be built with the |
88 | 88 | Tools/msi/buildrelease.bat script: |
89 | 89 |
|
90 | | - set PYTHON=<path to Python 2.7> |
| 90 | + set PYTHON=<path to Python 2.7 or 3.4> |
91 | 91 | set SPHINXBUILD=<path to sphinx-build.exe> |
92 | 92 | set PATH=<path to Mercurial (hg.exe)>; |
93 | 93 | <path to HTML Help Compiler (hhc.exe)>;%PATH% |
@@ -229,6 +229,11 @@ interest: |
229 | 229 | Every package should reference this property to include upgrade |
230 | 230 | information. |
231 | 231 |
|
| 232 | + OptionalFeature (Component) |
| 233 | + Packages that may be enabled or disabled should reference this component |
| 234 | + and have an OPTIONAL_FEATURES entry in the bootstrap application to |
| 235 | + properly handle Modify and Upgrade. |
| 236 | + |
232 | 237 | The .wxl_template file is specially handled by the build system for this |
233 | 238 | project to perform {{substitutions}} as defined in msi.targets. They |
234 | 239 | should be included in projects as <WxlTemplate> items, where .wxl files |
@@ -326,14 +331,11 @@ install directory. |
326 | 331 |
|
327 | 332 | .\python3x.dll The core interpreter |
328 | 333 | .\python3.dll The stable ABI reference |
329 | | -.\appcrt140.dll Microsoft Visual C Runtime |
330 | | -.\desktopcrt140.dll Microsoft Visual C Runtime |
331 | | -.\vcruntime140.dll Microsoft Visual C Runtime |
332 | 334 |
|
333 | 335 | When installed for all users, the following files are installed to |
334 | 336 | "%SystemRoot%" (typically "C:\Windows") to ensure they are always |
335 | 337 | available on PATH. (See Launching Python below.) For the current user, |
336 | | -they are installed in the Python install directory. |
| 338 | +they are installed in "%LocalAppData%\Programs\Python\PyLauncher". |
337 | 339 |
|
338 | 340 | .\py[w].exe PEP 397 launcher |
339 | 341 |
|
@@ -363,8 +365,10 @@ For 32-bit interpreters installed for the current user: |
363 | 365 |
|
364 | 366 | When the core Python executables are installed, a key "InstallPath" is |
365 | 367 | created within the root key with its default value set to the |
366 | | -executable's install directory. Within this key, a key "InstallGroup" is |
367 | | -created with its default value set to the product name "Python 3.X". |
| 368 | +executable's install directory. A value named "ExecutablePath" is added |
| 369 | +with the full path to the main Python interpreter, and a key |
| 370 | +"InstallGroup" is created with its default value set to the product |
| 371 | +name "Python 3.X". |
368 | 372 |
|
369 | 373 | When the Python standard library is installed, a key "PythonPath" is |
370 | 374 | created within the root key with its default value set to the full path |
|
0 commit comments