8 Commits

Author	SHA1	Message	Date
Martin v. Löwis	90f00ea624	Convert DOS files to CRLF. This doesn't touch the .hgeol settings, so that the files ... will have the right line ending even if the extension is not active.	2011-03-06 12:27:30 +01:00
Martin v. Löwis	416d31a5d2	Move amd64 properties further to the top, so that they override ... the linker options correctly.	2009-02-13 20:11:34 +00:00
Martin v. Löwis	a3e3cb7ee0	Issue #5134: Silence compiler warnings when compiling sqlite with VC++.	2009-02-10 13:09:19 +00:00
Martin v. Löwis	d84fd9599d	Issue #3215: Build sqlite3 as sqlite3.dll, not sqlite3.pyd	2008-06-30 06:57:39 +00:00
Martin v. Löwis	06510b2213	Run svneol.py on all sources.	2008-06-13 22:38:33 +00:00
Martin v. Löwis	cac8f585b1	Update AMD64 build for amalgamated sqlite.	2008-06-13 18:19:49 +00:00
Martin v. Löwis	cc0f2b20c5	Switch to SQLite 3.5.9.	2008-06-13 18:12:51 +00:00
Trent Nelson	05a96641b4	Refine the Visual Studio 2008 build solution in order to improve how we deal with external components, as well as fixing outstanding issues with Windows x64 build support. Introduce two new .vcproj files, _bsddb44.vcproj and sqlite3.vcproj, which replace the previous pre-link event scripts for _bsddb and _sqlite3 respectively. The new project files inherit from our property files as if they were any other Python module. This has numerous benefits. First, the components get built with exactly the same compiler flags and settings as the rest of Python. Second, it makes it much easier to debug problems in the external components when they're part of the build system. Third, they'll benefit from profile guided optimisation in the release builds, just like the rest of Python core. ... I've also introduced a slightly new pattern for managing externals in subversion. New components get checked in as <name>-<version>.x, where <version> matches the exact vendor version string. After the initial import of the external component, the .x is tagged as .0 (i.e. tcl-8.4.18.x -> tcl-8.4.18.0). Some components may not need any tweaking, whereas there are others that might (tcl/tk fall into this bucket). In that case, the relevant modifications are made to the .x branch, which will be subsequently tagged as .1 (and then n+1 going forward) when they build successfully and all tests pass. Buildbots will be converted to rely on these explicit tags only, which makes it easy for us to switch them over to a new version as and when required. (Simple change to external(-amd64).bat: if we've bumped tcl to 8.4.18.1, change the .bat to rmdir 8.4.18.0 if it exists and check out a new .1 copy.)	2008-03-19 07:45:19 +00:00