Building python 2.7.10 for Windows from source
I have been using Python for some time but it's been a decade since I've tried to build it from source, back in the 2.4 days. Things seem to have gotten a little more complicated now. I've read through the PCBuild/README file and got most stuff compiling. I find it a little odd that there are special instructions for the building the release version of tcl/tk. Is that what the developers actually do when they cut a release, or is there some other, top-level script that does this automatically? It just seems odd. Anyhow, my specific question is around the distutils wininst stubs, provided as binaries in the release tarball. Where can I find the source files that those binaries are built from? Many thanks, Mark.
On Jul 24, 2015 8:30 AM, "Mark Kelley" <keeely3@gmail.com> wrote:
I have been using Python for some time but it's been a decade since I've tried to build it from source, back in the 2.4 days. Things seem to have gotten a little more complicated now.
I've read through the PCBuild/README file and got most stuff compiling. I find it a little odd that there are special instructions for the building the release version of tcl/tk. Is that what the developers actually do when they cut a release, or is there some other, top-level script that does this automatically? It just seems odd.
That used to be standard procedure, yes. However, I just recently backported the project files from 3.5, which include project files for building Tcl/Tk and Tix, in both Debug and Release configurations, so I may have missed some stuff that could be removed from PCbuild/readme.txt. You do need some extra stuff to build 2.7 with its new project files, though (which i know is now covered in readme.txt). There hasn't been a release with those project files yet though, they're just in the hg repo.
Anyhow, my specific question is around the distutils wininst stubs, provided as binaries in the release tarball. Where can I find the source files that those binaries are built from?
I believe the source for those is in PC/bdist_wininst/, or some very similar path. Hope this helps, -- Zach (On a phone)
Thanks, that got me a bit further. Now I'm wondering how I figure out which version of tcl,tk and Tix actually got built with the 2.7.10 installer. Tools\buildbot\external.bat conflicts with the versions found in PC\build_tkinter.py, and the version in PC\VS8.0\build_tkinter.py. I am assuming the buildbot script is the one that's actually, used? I would submit a patch to clean some of this up, but sounds as though it's in the pipeline. On Fri, Jul 24, 2015 at 2:46 PM, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
On Jul 24, 2015 8:30 AM, "Mark Kelley" <keeely3@gmail.com> wrote:
I have been using Python for some time but it's been a decade since I've tried to build it from source, back in the 2.4 days. Things seem to have gotten a little more complicated now.
I've read through the PCBuild/README file and got most stuff compiling. I find it a little odd that there are special instructions for the building the release version of tcl/tk. Is that what the developers actually do when they cut a release, or is there some other, top-level script that does this automatically? It just seems odd.
That used to be standard procedure, yes. However, I just recently backported the project files from 3.5, which include project files for building Tcl/Tk and Tix, in both Debug and Release configurations, so I may have missed some stuff that could be removed from PCbuild/readme.txt. You do need some extra stuff to build 2.7 with its new project files, though (which i know is now covered in readme.txt). There hasn't been a release with those project files yet though, they're just in the hg repo.
Anyhow, my specific question is around the distutils wininst stubs, provided as binaries in the release tarball. Where can I find the source files that those binaries are built from?
I believe the source for those is in PC/bdist_wininst/, or some very similar path.
Hope this helps, -- Zach (On a phone)
On 7/27/2015 10:25 AM, Mark Kelley wrote:
Thanks, that got me a bit further. Now I'm wondering how I figure out which version of tcl,tk and Tix actually got built with the 2.7.10 installer.
This is really a python-list question, but for the PSF installer, tcl/tk 8.5.15 -- Terry Jan Reedy
I got my MSI built, after numerous modifications to the various build scripts. the installed file set bears little resemblance to the official release for the same version, which is a bit of a fail for the Open-source principle, but it seems nobody cares, so I'll split.
Those files should be under PC folder. Building 3.5 and onwards is a much more pleasant experience, and many of those improvements have been backported for 2.7.11. Cheers, Steve Top-posted from my Windows Phone ________________________________ From: Mark Kelley<mailto:keeely3@gmail.com> Sent: 7/24/2015 6:30 To: Python-Dev@python.org<mailto:Python-Dev@python.org> Subject: [Python-Dev] Building python 2.7.10 for Windows from source I have been using Python for some time but it's been a decade since I've tried to build it from source, back in the 2.4 days. Things seem to have gotten a little more complicated now. I've read through the PCBuild/README file and got most stuff compiling. I find it a little odd that there are special instructions for the building the release version of tcl/tk. Is that what the developers actually do when they cut a release, or is there some other, top-level script that does this automatically? It just seems odd. Anyhow, my specific question is around the distutils wininst stubs, provided as binaries in the release tarball. Where can I find the source files that those binaries are built from? Many thanks, Mark. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/steve.dower%40microsoft.c...
participants (4)
-
Mark Kelley -
Steve Dower -
Terry Reedy -
Zachary Ware