Lines Matching +full:build +full:- +full:python
1 Building Python using VC++ 7.1
2 -------------------------------------
3 This directory is used to build Python for Win32 platforms, e.g. Windows
10 the "Standard" toolbar"), and build the projects.
12 The proper order to build subprojects:
14 1) pythoncore (this builds the main Python DLL and library files,
19 2) python (this builds the main Python executable,
20 python.exe in Release mode)
23 want to build most of the other subprojects, unless you're building an
24 entire Python distribution from scratch, or specifically making changes
25 to the subsystems they implement, or are running a Python core buildbot
32 -----------
33 These subprojects should build out of the box. Subprojects other than the
34 main ones (pythoncore, python, pythonw) generally build a DLL (renamed to
40 python
43 pythonw.exe, a variant of python.exe that doesn't pop up a DOS box
47 tests of the Python C API, run via Lib/test/test_capi.py, and
50 Python wrapper for accelerated XML parsing, which incorporates stable
59 The following subprojects will generally NOT build out of the box. They
60 wrap code Python doesn't control, and you'll need to download the base
66 Python wrapper for the Tk windowing system. Requires building
70 ----------
72 svn export http://svn.python.org/projects/external/tcl8.4.12
73 svn export http://svn.python.org/projects/external/tk8.4.12
74 svn export http://svn.python.org/projects/external/tix-8.4.0
76 Build Tcl first (done here w/ MSVC 7.1 on Windows XP)
77 ---------------
78 Use "Start -> All Programs -> Microsoft Visual Studio .NET 2003
79 -> Visual Studio .NET Tools -> Visual Studio .NET 2003 Command Prompt"
82 nmake -f makefile.vc
83 nmake -f makefile.vc INSTALLDIR=..\..\tcltk install
88 nmake -f makefile.vc test
90 On WinXP Pro, wholly up to date as of 30-Aug-2004:
94 Build Tk
95 --------
97 nmake -f makefile.vc TCLDIR=..\..\tcl8.4.12
98 nmake -f makefile.vc TCLDIR=..\..\tcl8.4.12 INSTALLDIR=..\..\tcltk install
103 XXX directory. Is all of that really needed for Python use of Tcl/Tk?
106 nmake -f makefile.vc TCLDIR=..\..\tcl8.4.12 test
108 On WinXP Pro, wholly up to date as of 30-Aug-2004:
114 ---------
115 cd dist\tix-8.4.0\win
116 nmake -f python.mak
117 nmake -f python.mak install
120 Python wrapper for the libbz2 compression library. Homepage
122 Download the source from the python.org copy into the dist
125 svn export http://svn.python.org/projects/external/bzip2-1.0.3
127 A custom pre-link step in the bz2 project settings should manage to
128 build bzip2-1.0.3\libbz2.lib by magic before bz2.pyd (or bz2_d.pyd) is
131 bzip2-1.0.3\ when you do a clean, so if you want to rebuild bzip2.lib
132 you need to clean up bzip2-1.0.3\ by hand.
134 The build step shouldn't yield any warnings or errors, and should end
138 All of this managed to build bzip2-1.0.3\libbz2.lib, which the Python
143 To use the version of bsddb that Python is built with by default, invoke
146 svn export http://svn.python.org/projects/external/db-4.4.20
151 devenv db-4.4.20\build_win32\Berkeley_DB.sln /build Release /project db_static
153 and do that a second time for a Debug build too:
155 devenv db-4.4.20\build_win32\Berkeley_DB.sln /build Debug /project db_static
165 default, Python is built and distributed WITHOUT strong crypto.
167 Unpack the sources; if you downloaded the non-crypto version, rename
168 the directory from db-4.4.20.NC to db-4.4.20.
173 dist\db-4.4.20\docs\index.html
175 and follow the "Windows->Building Berkeley DB with Visual C++ .NET"
178 Build the "db_static" project, for "Release" mode.
180 To run extensive tests, pass "-u bsddb" to regrtest.py. test_bsddb3.py
187 XXX DBAgainError: (11, 'Resource temporarily unavailable -- unable
190 XXX and it appears timing-dependent. On Win2K I also saw this once:
195 XXX File "C:\Code\python\lib\threading.py", line 411, in __bootstrap
197 XXX File "C:\Code\python\lib\threading.py", line 399, in run
199 XXX File "C:\Code\python\lib\bsddb\test\test_thread.py", line 268, in
202 XXX DBLockDeadlockError: (-30996, 'DB_LOCK_DEADLOCK: Locker killed
210 - open a VS.NET 2003 command prompt
211 - run the SDK setenv.cmd script, passing /RETAIL and the target
213 - build BerkeleyDB with the solution configuration matching the
215 devenv db-4.4.20\build_win32\Berkeley_DB.sln /build "Release AMD64" /project db_static /useenv
218 Python wrapper for SQLite library.
222 svn export http://svn.python.org/projects/external/sqlite-source-3.3.4
224 To use the extension module in a Python build tree, copy sqlite3.dll into
228 Python wrapper for the secure sockets library.
232 svn export http://svn.python.org/projects/external/openssl-0.9.8a
235 You can (theoretically) use any version of OpenSSL you like - the
236 build process will automatically select the latest version.
240 as this is used by the OpenSSL build process. Complain to them <wink>.
243 the build. This Python script locates and builds your OpenSSL
244 installation, then invokes a simple makefile to build the final .pyd.
252 should be able to be run directly from the command-line.
254 build_ssl.py/MSVC isn't clever enough to clean OpenSSL - you must do
258 --------------------
262 SDK, in particular the 64-bit support. This includes an Itanium compiler
270 ------------------
272 The build process for the ReleaseAMD64 configuration is very similar
276 Building Python Using the free MS Toolkit Compiler
277 --------------------------------------------------
279 The build process for Visual C++ can be used almost unchanged with the free MS
280 Toolkit Compiler. This provides a way of building Python using freely
288 cannot be used to build a version of Python compatible with the standard
289 python.org build. If you are interested in using Visual C++ 2008 Express
294 To build Python, the following tools are required:
297 no longer available for download - see above
299 … from http://www.microsoft.com/downloads/details.aspx?FamilyID=484269e2-3b89-47e3-8eb7-1f2be6d7123a
301 … from http://www.microsoft.com/downloads/details.aspx?FamilyID=9b3a2ca6-3647-4070-9f41-a333c6b9181d
306 compiler supplied with the .NET SDK is a non-optimising version). The
308 (the Windows 2003 Server SP1 edition, typical install, is known to work -
316 If you intend to build the openssl (needed for the _ssl extension) you
322 "nightly build" versions are known NOT to work - it is not clear at
327 Start a platform SDK "build environment window" from the start menu. The
328 "Windows XP 32-bit retail" version is known to work.
354 "win64" directory are 32-bit programs, so they are fine to use here.
356 That's it. To build Python (the core only, no binary extensions which
359 nant -buildfile:python.build all
365 To build those extension modules which require external libraries
367 for the Visual Studio build above, with a few minor modifications. These
368 instructions have only been tested using the sources in the Python
369 subversion repository - building from original sources should work, but
372 For each extension module you wish to build, you should remove the
373 associated include line from the excludeprojects section of pc.build.
378 The tix makefile (tix-8.4.0\win\makefile.vc) must be modified to
384 The remainder of the build instructions will work as given.
390 The file db.build should be copied from the Python PCBuild directory
391 to the directory db-4.4.20\build_win32.
393 The file db_static.vcproj in db-4.4.20\build_win32 should be edited to
394 remove the string "$(SolutionDir)" - this occurs in 2 places, only
395 relevant for 64-bit builds. (The edit is required as otherwise, nant
398 The bsddb library can then be build with the command
399 nant -buildfile:db.build all
400 run from the db-4.4.20\build_win32 directory.
405 python.exe.
408 The documented build process works as written. However, it needs a
411 build setargv.obj, proceed as follows:
419 With setargv.obj in place, the standard build process should work
423 -----------------------
425 with easy-to-follow instructions in ../PC/example/; read the file