Lines Matching +full:build +full:- +full:packages
1 Quick Build Info
4 For testing, the installer should be built with the Tools/msi/build.bat
7 build.bat [-x86] [-x64] [--doc]
13 set SPHINXBUILD=<path to sphinx-build.exe>
17 buildrelease.bat [-x86] [-x64] [-D] [-B]
18 [-o <output directory>] [-c <certificate name>]
27 without having to build it themselves.
46 and command-line logic, as well as the ability to locate and optionally
65 Before building the installer, download extra build dependencies using
77 For testing, the installer should be built with the Tools/msi/build.bat
80 build.bat [-x86] [-x64] [--doc] [--test-marker] [--pack]
82 This script will build the required configurations of Python and
83 generate an installer layout in PCbuild/(win32|amd64)/en-us.
85 Specify -x86 and/or -x64 to build for each platform. If neither is
89 Specify --doc to build the documentation (.chm) file. If the file is not
95 Specify --test-marker to build an installer that works side-by-side with
100 Specify --pack to build an installer that does not require all MSIs to
108 set SPHINXBUILD=<path to sphinx-build.exe>
112 buildrelease.bat [-x86] [-x64] [-D] [-B]
113 [-o <output directory>] [-c <certificate name>]
115 Specify -x86 and/or -x64 to build for each platform. If neither is
119 Specify -D to skip rebuilding the documentation. The documentation is
120 required for a release and the build will fail if it is not available.
122 Specify -B to skip rebuilding Python. This is useful to only rebuild the
125 Specify -o to set an output directory. The installer layouts will be
126 copied to platform-specific subdirectories of this path.
128 Specify -c to choose a code-signing certificate to be used for all the
140 To manually build layouts of the installer, build one of the projects in
163 to generate MinGW-compatible libraries, and the build will be aborted if
167 Used to generate unique IDs for the installers to allow side-by-side
176 can be downloaded from. The build version and architecture will be
205 path or have run get_externals.bat. You may also need to "gpg2.exe --import"
208 uploadrelease.bat --host <host> --user <username> [--dry-run] [--no-gpg]
216 Use --dry-run to display the generated upload commands without executing
218 --no-gpg is also passed.
220 Use --no-gpg to suppress signature generation and upload.
224 --target <path> for other purposes. This path should generally not include
230 The code for the installer is divided into three main groups: packages,
233 Packages
234 --------
236 Packages appear as subdirectories of Tools/msi (other than the bundle/
237 directory). The project file is a .wixproj and the build output is a
238 single MSI. Packages are built with the WiX Toolset. Some project files
241 files are related, but produce multiple independent packages.
249 some packages may not install any files. For example, the pip package
253 library" option, for example.) Dependencies between packages are handled
254 by the bundle, but packages should detect when dependencies are missing
257 Packages that include a lot of files may use an InstallFiles element in
263 All packages are built with the Tools/msi/common.wxs file, and so any
282 Packages that may be enabled or disabled should reference this component
286 The .wxl_template file is specially handled by the build system for this
292 ------
296 with packages references in Tools/msi/bundle/packagegroups.
298 Build logic for the bundle is in bundle.targets, but should be invoked
304 Bundle.wxs also contains the chain, which is the list of packages to
308 Each package group specifies one or more packages to install. Most
309 packages require two separate entries to support both per-user and
310 all-users installations. Because these reuse the same package, it does
322 MSI packages are installed or uninstalled based on their current state
326 EXE packages are executed based on a customisable condition that can be
327 omitted. This makes them suitable for pre- or post-install tasks that
331 ---------------------
350 "%ProgramFiles%\Python3X" for the 64-bit interpreter and
351 "%ProgramFiles(x86)%\Python3X-32" for the 32-bit interpreter. (Note that
352 the latter path is equivalent to "%ProgramFiles%\Python3X-32" when
353 running a 32-bit version of Windows.) This location requires
357 is "%LocalAppData%\Programs\Python\Python3X" for the 64-bit interpreter
358 and "%LocalAppData%\Programs\Python\Python3X-32" for the 32-bit
400 For 64-bit interpreters installed for all users, the root key is:
403 For 32-bit interpreters installed for all users on a 64-bit operating
405 HKEY_LOCAL_MACHINE\Software\Wow6432Node\Python\PythonCore\3.X-32
407 For 32-bit interpreters installed for all users on a 32-bit operating
409 HKEY_LOCAL_MACHINE\Software\Python\PythonCore\3.X-32
411 For 64-bit interpreters installed for the current user:
414 For 32-bit interpreters installed for the current user:
415 HKEY_CURRENT_USER\Software\Python\PythonCore\3.X-32
439 When installed for all users on a 64-bit operating system, the
443 When installed for all users on a 32-bit operating system, the
464 The core Python executables creates a shortcut "Python 3.X (32-bit)" or
465 "Python 3.X (64-bit)" depending on the interpreter.
467 The documentation creates a shortcut "Python 3.X 32-bit Manuals" or
468 "Python 3.X 64-bit Manuals". The documentation is identical for all
472 Installing IDLE creates a shortcut "IDLE (Python 3.X 32-bit)" or "IDLE
473 (Python 3.X 64-bit)" depending on the interpreter.
480 for an all users install and the user PATH for a per-user install.
484 the user PATH, users cannot override a system-wide installation of
492 preferred order. System-wide installations of Python should consider not
499 preferred over system-wide installs, and later versions are preferred
501 currently prefers 2.x versions over 3.x versions without the -3 command
504 For both 32-bit and 64-bit interpreters, the 32-bit version of the
506 consistent (as the 64-bit launcher is subtly different from the 32-bit
508 versions of Python will upgrade the launcher in-place, using Windows
527 Windows Installer caches installation packages, removing features will
535 the cached packages have been corrupted or deleted.
539 explicitly handled by the installer. Python packages installed later