Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 1 | Building Python using VC++ 9.0 |
| 2 | ------------------------------ |
Christian Heimes | d9fbab2 | 2008-01-02 17:43:40 +0000 | [diff] [blame] | 3 | |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 4 | This directory is used to build Python for Win32 platforms, e.g. Windows |
| 5 | 2000, XP and Vista. It requires Microsoft Visual C++ 9.0 |
| 6 | (a.k.a. Visual Studio .NET 2008). |
| 7 | (For other Windows platforms and compilers, see ../PC/readme.txt.) |
| 8 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 9 | All you need to do is open the workspace "pcbuild.sln" in Visual Studio, |
| 10 | select the desired combination of configuration and platform and eventually |
| 11 | build the solution. Unless you are going to debug a problem in the core or |
| 12 | you are going to create an optimized build you want to select "Release" as |
| 13 | configuration. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 14 | |
Christian Heimes | 3adfe9a | 2007-12-31 15:18:55 +0000 | [diff] [blame] | 15 | The PCbuild directory is compatible with all versions of Visual Studio from |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 16 | VS C++ Express Edition over the standard edition up to the professional |
| 17 | edition. However the express edition does support features like solution |
| 18 | folders or profile guided optimization (PGO). The missing bits and pieces |
| 19 | won't stop you from building Python. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 20 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 21 | The solution is configured to build the projects in the correct order. "Build |
Christian Heimes | 95d6447 | 2008-02-09 19:55:22 +0000 | [diff] [blame] | 22 | Solution" or F7 takes care of dependencies except for x64 builds. To make |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 23 | cross compiling x64 builds on a 32bit OS possible the x64 builds require a |
| 24 | 32bit version of Python. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 25 | |
Christian Heimes | 3971f6b | 2007-11-30 19:18:08 +0000 | [diff] [blame] | 26 | NOTE: |
| 27 | You probably don't want to build most of the other subprojects, unless |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 28 | you're building an entire Python distribution from scratch, or |
| 29 | specifically making changes to the subsystems they implement, or are |
| 30 | running a Python core buildbot test slave; see SUBPROJECTS below) |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 31 | |
| 32 | When using the Debug setting, the output files have a _d added to |
Christian Heimes | 95d6447 | 2008-02-09 19:55:22 +0000 | [diff] [blame] | 33 | their name: python30_d.dll, python_d.exe, parser_d.pyd, and so on. Both |
| 34 | the build and rt batch files accept a -d option for debug builds. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 35 | |
Christian Heimes | 3adfe9a | 2007-12-31 15:18:55 +0000 | [diff] [blame] | 36 | The 32bit builds end up in the solution folder PCbuild while the x64 builds |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 37 | land in the amd64 subfolder. The PGI and PGO builds for profile guided |
| 38 | optimization end up in their own folders, too. |
| 39 | |
Christian Heimes | d9fbab2 | 2008-01-02 17:43:40 +0000 | [diff] [blame] | 40 | Legacy support |
| 41 | -------------- |
| 42 | |
| 43 | You can find build directories for older versions of Visual Studio and |
| 44 | Visual C++ in the PC directory. The legacy build directories are no longer |
| 45 | actively maintained and may not work out of the box. |
| 46 | |
| 47 | PC/VC6/ |
| 48 | Visual C++ 6.0 |
| 49 | PC/VS7.1/ |
| 50 | Visual Studio 2003 (7.1) |
| 51 | PCbuild8/ |
| 52 | Visual Studio 2005 (8.0) |
| 53 | |
| 54 | |
| 55 | C RUNTIME |
| 56 | --------- |
| 57 | |
| 58 | Visual Studio 2008 uses version 9 of the C runtime (MSVCRT9). The executables |
| 59 | are linked to a CRT "side by side" assembly which must be present on the target |
| 60 | machine. This is avalible under the VC/Redist folder of your visual studio |
| 61 | distribution. On XP and later operating systems that support |
| 62 | side-by-side assemblies it is not enough to have the msvcrt80.dll present, |
| 63 | it has to be there as a whole assembly, that is, a folder with the .dll |
| 64 | and a .manifest. Also, a check is made for the correct version. |
| 65 | Therefore, one should distribute this assembly with the dlls, and keep |
| 66 | it in the same directory. For compatibility with older systems, one should |
| 67 | also set the PATH to this directory so that the dll can be found. |
| 68 | For more info, see the Readme in the VC/Redist folder. |
| 69 | |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 70 | SUBPROJECTS |
| 71 | ----------- |
| 72 | These subprojects should build out of the box. Subprojects other than the |
| 73 | main ones (pythoncore, python, pythonw) generally build a DLL (renamed to |
| 74 | .pyd) from a specific module so that users don't have to load the code |
| 75 | supporting that module unless they import the module. |
| 76 | |
| 77 | pythoncore |
| 78 | .dll and .lib |
| 79 | python |
| 80 | .exe |
| 81 | pythonw |
| 82 | pythonw.exe, a variant of python.exe that doesn't pop up a DOS box |
| 83 | _socket |
| 84 | socketmodule.c |
| 85 | _testcapi |
| 86 | tests of the Python C API, run via Lib/test/test_capi.py, and |
| 87 | implemented by module Modules/_testcapimodule.c |
| 88 | pyexpat |
| 89 | Python wrapper for accelerated XML parsing, which incorporates stable |
| 90 | code from the Expat project: http://sourceforge.net/projects/expat/ |
| 91 | select |
| 92 | selectmodule.c |
| 93 | unicodedata |
| 94 | large tables of Unicode data |
| 95 | winsound |
| 96 | play sounds (typically .wav files) under Windows |
| 97 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 98 | The following subprojects will generally NOT build out of the box. They |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 99 | wrap code Python doesn't control, and you'll need to download the base |
| 100 | packages first and unpack them into siblings of PCbuilds's parent |
Christian Heimes | 3adfe9a | 2007-12-31 15:18:55 +0000 | [diff] [blame] | 101 | directory; for example, if your PCbuild is ..\dist\py3k\PCbuild\, |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 102 | unpack into new subdirectories of ..\dist\. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 103 | |
| 104 | _tkinter |
| 105 | Python wrapper for the Tk windowing system. Requires building |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 106 | Tcl/Tk first. Following are instructions for Tcl/Tk 8.4.16. |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 107 | |
| 108 | NOTE: The 64 build builds must land in tcltk64 instead of tcltk. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 109 | |
| 110 | Get source |
| 111 | ---------- |
| 112 | In the dist directory, run |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 113 | svn export http://svn.python.org/projects/external/tcl8.4.16 |
| 114 | svn export http://svn.python.org/projects/external/tk8.4.16 |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 115 | svn export http://svn.python.org/projects/external/tix-8.4.0 |
| 116 | |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 117 | Build with build_tkinter.py |
| 118 | --------------------------- |
Christian Heimes | 3adfe9a | 2007-12-31 15:18:55 +0000 | [diff] [blame] | 119 | The PCbuild directory contains a Python script which automates all |
Thomas Heller | 44c38c1 | 2008-01-10 18:45:40 +0000 | [diff] [blame] | 120 | steps. Run the script in a Visual Studio 2008 command prompt with |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 121 | |
| 122 | python build_tkinter.py Win32 |
| 123 | |
| 124 | Use x64 instead of Win32 for the x64 platform. |
| 125 | |
Christian Heimes | 95d6447 | 2008-02-09 19:55:22 +0000 | [diff] [blame] | 126 | NOTE: Tcl/Tk 8.4 doesn't compile for x64. |
| 127 | |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 128 | Build Tcl first |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 129 | --------------- |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 130 | Use "Start -> All Programs -> Microsoft Visual Studio 2008 |
| 131 | -> Visual Studio Tools -> Visual Studio 2008 Command Prompt" |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 132 | to get a shell window with the correct environment settings |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 133 | cd dist\tcl8.4.16\win |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 134 | nmake -f makefile.vc |
| 135 | nmake -f makefile.vc INSTALLDIR=..\..\tcltk install |
| 136 | |
| 137 | XXX Should we compile with OPTS=threads? |
| 138 | |
| 139 | Optional: run tests, via |
| 140 | nmake -f makefile.vc test |
| 141 | |
| 142 | On WinXP Pro, wholly up to date as of 30-Aug-2004: |
| 143 | all.tcl: Total 10678 Passed 9969 Skipped 709 Failed 0 |
| 144 | Sourced 129 Test Files. |
| 145 | |
| 146 | Build Tk |
| 147 | -------- |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 148 | cd dist\tk8.4.16\win |
| 149 | nmake -f makefile.vc TCLDIR=..\..\tcl8.4.16 |
| 150 | nmake -f makefile.vc TCLDIR=..\..\tcl8.4.16 INSTALLDIR=..\..\tcltk install |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 151 | |
| 152 | XXX Should we compile with OPTS=threads? |
| 153 | |
| 154 | XXX Our installer copies a lot of stuff out of the Tcl/Tk install |
| 155 | XXX directory. Is all of that really needed for Python use of Tcl/Tk? |
| 156 | |
| 157 | Optional: run tests, via |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 158 | nmake -f makefile.vc TCLDIR=..\..\tcl8.4.16 test |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 159 | |
| 160 | On WinXP Pro, wholly up to date as of 30-Aug-2004: |
| 161 | all.tcl: Total 8420 Passed 6826 Skipped 1581 Failed 13 |
| 162 | Sourced 91 Test Files. |
| 163 | Files with failing tests: canvImg.test scrollbar.test textWind.test winWm.test |
| 164 | |
| 165 | Built Tix |
| 166 | --------- |
| 167 | cd dist\tix-8.4.0\win |
Christian Heimes | 4c07cd9 | 2007-12-05 19:57:54 +0000 | [diff] [blame] | 168 | nmake -f python9.mak |
| 169 | nmake -f python9.mak install |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 170 | |
| 171 | bz2 |
| 172 | Python wrapper for the libbz2 compression library. Homepage |
| 173 | http://sources.redhat.com/bzip2/ |
| 174 | Download the source from the python.org copy into the dist |
| 175 | directory: |
| 176 | |
| 177 | svn export http://svn.python.org/projects/external/bzip2-1.0.3 |
| 178 | |
| 179 | A custom pre-link step in the bz2 project settings should manage to |
| 180 | build bzip2-1.0.3\libbz2.lib by magic before bz2.pyd (or bz2_d.pyd) is |
Christian Heimes | 3adfe9a | 2007-12-31 15:18:55 +0000 | [diff] [blame] | 181 | linked in PCbuild\. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 182 | However, the bz2 project is not smart enough to remove anything under |
| 183 | bzip2-1.0.3\ when you do a clean, so if you want to rebuild bzip2.lib |
| 184 | you need to clean up bzip2-1.0.3\ by hand. |
| 185 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 186 | All of this managed to build libbz2.lib in |
| 187 | bzip2-1.0.3\$platform-$configuration\, which the Python project links in. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 188 | |
| 189 | |
| 190 | _bsddb |
| 191 | To use the version of bsddb that Python is built with by default, invoke |
| 192 | (in the dist directory) |
| 193 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 194 | svn export http://svn.python.org/projects/external/db-4.4.20 |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 195 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 196 | Next open the solution file db-4.4.20\build_win32\Berkeley_DB.sln with |
Christian Heimes | 3af3ecc | 2008-02-03 14:34:18 +0000 | [diff] [blame] | 197 | Visual Studio and convert the projects to the new format. VS 2008 |
| 198 | builds the necessary libraries in a pre-link step of _bsddb. You |
| 199 | have to add "$(VCInstallDir)vcpackages" to the search path first |
| 200 | (Tools -> Options -> Projects and Solutions -> VC++ Directories, |
| 201 | Platform: Win32, Show directories for: Executable files). |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 202 | |
| 203 | The _bsddb subprojects depends only on the db_static project of |
| 204 | Berkeley DB. You have to choose either "Release", "Release AMD64", "Debug" |
| 205 | or "Debug AMD64" as configuration. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 206 | |
| 207 | Alternatively, if you want to start with the original sources, |
| 208 | go to Sleepycat's download page: |
| 209 | http://www.sleepycat.com/downloads/releasehistorybdb.html |
| 210 | |
| 211 | and download version 4.4.20. |
| 212 | |
| 213 | With or without strong cryptography? You can choose either with or |
| 214 | without strong cryptography, as per the instructions below. By |
| 215 | default, Python is built and distributed WITHOUT strong crypto. |
| 216 | |
| 217 | Unpack the sources; if you downloaded the non-crypto version, rename |
| 218 | the directory from db-4.4.20.NC to db-4.4.20. |
| 219 | |
| 220 | Now apply any patches that apply to your version. |
| 221 | |
| 222 | Open |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 223 | db-4.4.20\docs\ref\build_win\intro.html |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 224 | |
| 225 | and follow the "Windows->Building Berkeley DB with Visual C++ .NET" |
| 226 | instructions for building the Sleepycat |
| 227 | software. Note that Berkeley_DB.dsw is in the build_win32 subdirectory. |
| 228 | Build the "db_static" project, for "Release" mode. |
| 229 | |
| 230 | To run extensive tests, pass "-u bsddb" to regrtest.py. test_bsddb3.py |
| 231 | is then enabled. Running in verbose mode may be helpful. |
| 232 | |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 233 | _sqlite3 |
| 234 | Python wrapper for SQLite library. |
| 235 | |
| 236 | Get the source code through |
| 237 | |
| 238 | svn export http://svn.python.org/projects/external/sqlite-source-3.3.4 |
| 239 | |
| 240 | To use the extension module in a Python build tree, copy sqlite3.dll into |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 241 | the PCbuild folder. The source directory in svn also contains a .def file |
| 242 | from the binary release of sqlite3. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 243 | |
| 244 | _ssl |
| 245 | Python wrapper for the secure sockets library. |
| 246 | |
| 247 | Get the source code through |
| 248 | |
| 249 | svn export http://svn.python.org/projects/external/openssl-0.9.8g |
| 250 | |
| 251 | Alternatively, get the latest version from http://www.openssl.org. |
| 252 | You can (theoretically) use any version of OpenSSL you like - the |
| 253 | build process will automatically select the latest version. |
| 254 | |
Christian Heimes | 3971f6b | 2007-11-30 19:18:08 +0000 | [diff] [blame] | 255 | You must install the NASM assembler from |
| 256 | http://www.kernel.org/pub/software/devel/nasm/binaries/win32/ |
| 257 | for x86 builds. Put nasmw.exe anywhere in your PATH. |
| 258 | |
| 259 | You can also install ActivePerl from |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 260 | http://www.activestate.com/Products/ActivePerl/ |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 261 | if you like to use the official sources instead of the files from |
| 262 | python's subversion repository. The svn version contains pre-build |
| 263 | makefiles and assembly files. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 264 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 265 | The build process makes sure that no patented algorithms are included. |
| 266 | For now RC5, MDC2 and IDEA are excluded from the build. You may have |
| 267 | to manually remove $(OBJ_D)\i_*.obj from ms\nt.mak if the build process |
| 268 | complains about missing files or forbidden IDEA. Again the files provided |
| 269 | in the subversion repository are already fixed. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 270 | |
| 271 | The MSVC project simply invokes PCBuild/build_ssl.py to perform |
| 272 | the build. This Python script locates and builds your OpenSSL |
| 273 | installation, then invokes a simple makefile to build the final .pyd. |
| 274 | |
| 275 | build_ssl.py attempts to catch the most common errors (such as not |
| 276 | being able to find OpenSSL sources, or not being able to find a Perl |
| 277 | that works with OpenSSL) and give a reasonable error message. |
| 278 | If you have a problem that doesn't seem to be handled correctly |
| 279 | (eg, you know you have ActivePerl but we can't find it), please take |
| 280 | a peek at build_ssl.py and suggest patches. Note that build_ssl.py |
| 281 | should be able to be run directly from the command-line. |
| 282 | |
| 283 | build_ssl.py/MSVC isn't clever enough to clean OpenSSL - you must do |
| 284 | this by hand. |
| 285 | |
| 286 | Building for Itanium |
| 287 | -------------------- |
| 288 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 289 | NOTE: |
| 290 | Official support for Itanium builds have been dropped from the build. Please |
Christian Heimes | 95d6447 | 2008-02-09 19:55:22 +0000 | [diff] [blame] | 291 | contact us and provide patches if you are interested in Itanium builds. |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 292 | |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 293 | The project files support a ReleaseItanium configuration which creates |
| 294 | Win64/Itanium binaries. For this to work, you need to install the Platform |
| 295 | SDK, in particular the 64-bit support. This includes an Itanium compiler |
| 296 | (future releases of the SDK likely include an AMD64 compiler as well). |
| 297 | In addition, you need the Visual Studio plugin for external C compilers, |
| 298 | from http://sf.net/projects/vsextcomp. The plugin will wrap cl.exe, to |
| 299 | locate the proper target compiler, and convert compiler options |
| 300 | accordingly. The project files require atleast version 0.9. |
| 301 | |
| 302 | Building for AMD64 |
| 303 | ------------------ |
| 304 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 305 | The build process for AMD64 / x64 is very similar to standard builds. You just |
Martin v. Löwis | 9e05135 | 2008-02-29 18:54:45 +0000 | [diff] [blame^] | 306 | have to set x64 as platform. In addition, the HOST_PYTHON environment variable |
| 307 | must point to a Python interpreter (at least 2.4), to support cross-compilation. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 308 | |
| 309 | Building Python Using the free MS Toolkit Compiler |
| 310 | -------------------------------------------------- |
| 311 | |
Christian Heimes | 3971f6b | 2007-11-30 19:18:08 +0000 | [diff] [blame] | 312 | Microsoft has withdrawn the free MS Toolkit Compiler, so this can no longer |
| 313 | be considered a supported option. Instead you can use the free VS C++ Express |
| 314 | Edition. |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 315 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 316 | Profile Guided Optimization |
| 317 | --------------------------- |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 318 | |
Thomas Heller | 44c38c1 | 2008-01-10 18:45:40 +0000 | [diff] [blame] | 319 | The solution has two configurations for PGO. The PGInstrument |
| 320 | configuration must be build first. The PGInstrument binaries are |
| 321 | lniked against a profiling library and contain extra debug |
| 322 | information. The PGUpdate configuration takes the profiling data and |
| 323 | generates optimized binaries. |
Christian Heimes | 3d2f564 | 2007-12-06 21:13:06 +0000 | [diff] [blame] | 324 | |
| 325 | The build_pgo.bat script automates the creation of optimized binaries. It |
| 326 | creates the PGI files, runs the unit test suite or PyBench with the PGI |
| 327 | python and finally creates the optimized files. |
| 328 | |
Christian Heimes | 8b01140 | 2007-11-27 21:28:40 +0000 | [diff] [blame] | 329 | http://msdn2.microsoft.com/en-us/library/e7k32f4k(VS.90).aspx |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 330 | |
Christian Heimes | 3971f6b | 2007-11-30 19:18:08 +0000 | [diff] [blame] | 331 | Static library |
| 332 | -------------- |
| 333 | |
| 334 | The solution has no configuration for static libraries. However it is easy |
| 335 | it build a static library instead of a DLL. You simply have to set the |
| 336 | "Configuration Type" to "Static Library (.lib)" and alter the preprocessor |
| 337 | macro "Py_ENABLE_SHARED" to "Py_NO_ENABLE_SHARED". You may also have to |
| 338 | change the "Runtime Library" from "Multi-threaded DLL (/MD)" to |
| 339 | "Multi-threaded (/MT)". |
| 340 | |
Christian Heimes | 1867994 | 2007-12-05 21:57:25 +0000 | [diff] [blame] | 341 | Visual Studio properties |
| 342 | ------------------------ |
| 343 | |
Christian Heimes | 3adfe9a | 2007-12-31 15:18:55 +0000 | [diff] [blame] | 344 | The PCbuild solution makes heavy use of Visual Studio property files |
Christian Heimes | 1867994 | 2007-12-05 21:57:25 +0000 | [diff] [blame] | 345 | (*.vsprops). The properties can be viewed and altered in the Property |
| 346 | Manager (View -> Other Windows -> Property Manager). |
| 347 | |
Christian Heimes | 3d2f564 | 2007-12-06 21:13:06 +0000 | [diff] [blame] | 348 | * debug (debug macro: _DEBUG) |
Christian Heimes | 1867994 | 2007-12-05 21:57:25 +0000 | [diff] [blame] | 349 | * pginstrument (PGO) |
| 350 | * pgupdate (PGO) |
| 351 | +-- pginstrument |
| 352 | * pyd (python extension, release build) |
| 353 | +-- release |
| 354 | +-- pyproject |
| 355 | * pyd_d (python extension, debug build) |
| 356 | +-- debug |
| 357 | +-- pyproject |
Christian Heimes | 3d2f564 | 2007-12-06 21:13:06 +0000 | [diff] [blame] | 358 | * pyproject (base settings for all projects, user macros like PyDllName) |
| 359 | * release (release macro: NDEBUG) |
Christian Heimes | 1867994 | 2007-12-05 21:57:25 +0000 | [diff] [blame] | 360 | * x64 (AMD64 / x64 platform specific settings) |
| 361 | |
| 362 | The pyproject propertyfile defines _WIN32 and x64 defines _WIN64 and _M_X64 |
| 363 | although the macros are set by the compiler, too. The GUI doesn't always know |
| 364 | about the macros and confuse the user with false information. |
| 365 | |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 366 | YOUR OWN EXTENSION DLLs |
| 367 | ----------------------- |
Christian Heimes | 3d2f564 | 2007-12-06 21:13:06 +0000 | [diff] [blame] | 368 | |
Christian Heimes | e8954f8 | 2007-11-22 11:21:16 +0000 | [diff] [blame] | 369 | If you want to create your own extension module DLL, there's an example |
| 370 | with easy-to-follow instructions in ../PC/example/; read the file |
| 371 | readme.txt there first. |