Lines Matching +full:visual +full:- +full:runtime +full:- +full:tests
2 -----------------
4 1. Install Microsoft Visual Studio 2008, any edition.
5 2. Install Microsoft Visual Studio 2010, any edition, or Windows SDK 7.1
6 and any version of Microsoft Visual Studio newer than 2010.
8 get_externals.bat (build.bat -e) will download and use Python via
10 3. Run "build.bat -e" to build Python in 32-bit Release configuration.
11 4. (Optional, but recommended) Run the test suite with "rt.bat -q".
15 ------------------------------------------
22 Visual Studio 2008 and Visual Studio 2010. Another configuration proven
23 to work is Visual Studio 2008, Windows SDK 7.1, and Visual Studio 2013.
25 If you only have Visual Studio 2008 available, use the project files in
28 If you do not have Visual Studio 2008 available, you can use these project
33 to build using MSVC10 (Visual Studio 2010).
49 Visual Studio, select the desired combination of configuration and platform,
58 used to build standard x86-compatible 32-bit binaries, output into this
59 directory. The x64 platform is used for building 64-bit AMD64 (aka
60 x86_64 or EM64T) binaries, output into the amd64 sub-directory. The
61 Itanium (IA-64) platform is no longer supported.
66 to using ./configure --with-pydebug on UNIX. All binaries built
69 build and rt (run test) batch files in this directory accept a -d
74 requires Professional Edition of Visual Studio 2008. See the
77 sub-directory of this directory. The official Python releases may
85 ----------------------------------------------
89 script to detect one of Visual Studio 2015, 2013, 2012, or 2010, any of
93 the 32-bit Win32 platform. It accepts several arguments to change
94 this behavior, try `build.bat -h` to learn more.
98 --------------
100 You can find build directories for older versions of Visual Studio and
101 Visual C++ in the PC directory. The project files in PC/VS9.0/ are
102 specific to Visual Studio 2008, and will be fully supported for the life
109 Visual C++ 6.0
111 Visual Studio 2003 (7.1)
113 Visual Studio 2005 (8.0)
116 C Runtime
117 ---------
119 Visual Studio 2008 uses version 9 of the C runtime (MSVCRT9). The executables
121 machine. This is available under the VC/Redist folder of your visual studio
123 side-by-side assemblies it is not enough to have the msvcrt90.dll present,
132 Sub-Projects
133 ------------
135 The CPython project is split up into several smaller sub-projects which
136 are managed by the pcbuild.sln solution file. Each sub-project is
138 name of the sub-project. These sub-projects fall into a few general
141 The following sub-projects represent the bare minimum required to build
149 These sub-projects provide extra executables that are useful for running
161 The following sub-projects are for individual modules of the standard
180 The following Python-controlled sub-projects wrap external projects.
184 about getting the source for building these libraries. The sub-projects
189 http://www.oracle.com/us/products/database/berkeley-db/
204 need a later version of NASM. If OpenSSL's self tests don't pass,
208 libeay/ssleay sub-projects use.
210 The libeay/ssleay sub-projects expect your OpenSSL sources to have
216 PCbuild\prepare_ssl.py path\to\openssl-source-dir
224 The libeay and ssleay sub-projects will build the modules of OpenSSL
248 The tcl, tk, and tix sub-projects do not clean their builds with
254 ------------------------
256 The last category of sub-projects listed above wrap external projects
261 directory. This script extracts all the external sub-projects from
262 https://github.com/python/cpython-source-deps
264 https://github.com/python/cpython-bin-deps
280 you pass the '-e' option to it.
284 ---------------------------
297 http://msdn.microsoft.com/en-us/library/e7k32f4k(VS.90).aspx
302 --------------
308 also have to change the "Runtime Library" from "Multi-threaded DLL
309 (/MD)" to "Multi-threaded (/MT)".
312 Visual Studio properties
313 ------------------------
315 The PCbuild solution makes use of Visual Studio property files (*.props)
317 Manager (View -> Other Windows -> Property Manager) but should be