Hello,
I was recently cleaning up my buildbot, clearing space, removing unused software, ..., and decided to remove MSVC 2010 as no supported Python uses that compiler. Well, to my surprise, actually I forgot, you do need MSVC 2010 *AND* 2008 to build 2.7 by default. It has been since reinstalled and the buildbot is chugging along happily.
With that, do we have any buildbots that use *just* 2008? Or does the 2.7 compiler package from Microsoft contain the needed bits that are provided by installing Visual Studio 2010?
I think my buildslave has enough resources to support another builder for that configuration (VC9 only) if that is something we are interested in doing.
Thanks
-- Jeremy Kloth
Hi Jeremy,
On Thu, Nov 3, 2016 at 1:40 PM, Jeremy Kloth <jeremy.kloth@gmail.com> wrote:
Hello,
I was recently cleaning up my buildbot, clearing space, removing unused software, ..., and decided to remove MSVC 2010 as no supported Python uses that compiler. Well, to my surprise, actually I forgot, you do need MSVC 2010 *AND* 2008 to build 2.7 by default. It has been since reinstalled and the buildbot is chugging along happily.
With that, do we have any buildbots that use *just* 2008? Or does the 2.7 compiler package from Microsoft contain the needed bits that are provided by installing Visual Studio 2010?
Unfortunately, the bits needed from VS 2010 are entirely separate from the bits provided by the 2.7 compiler package; the compiler package is more closely related to VS 2008, but still missing some important pieces.
I think my buildslave has enough resources to support another builder for that configuration (VC9 only) if that is something we are interested in doing.
I am in fact interested in doing so; there have been a couple of issues raised recently about the PC/VS9.0 files being left behind. I may also add a VS2008-only builder to the XP bot, since it's only running 2.7 anymore anyways.
-- Zach
Interesting - I probably would have assumed removing 2010 was safe for 2.7 as well. However, all of my 2.7 builders (XP/7/8/10) currently have both 2008 and 2010 so any dependency on 2010 would go unnoticed.
Assuming the 2010 dependency is unintentional, or we specifically want to test without it, the XP slave no longer builds anything but 2.7, so I could actually uninstall 2010 from that machine without affecting any other builders, or requiring any special configuration to avoid a 2010 installation.
-- David
On Thu, Nov 3, 2016 at 2:40 PM, Jeremy Kloth <jeremy.kloth@gmail.com> wrote:
Hello,
I was recently cleaning up my buildbot, clearing space, removing unused software, ..., and decided to remove MSVC 2010 as no supported Python uses that compiler. Well, to my surprise, actually I forgot, you do need MSVC 2010 *AND* 2008 to build 2.7 by default. It has been since reinstalled and the buildbot is chugging along happily.
With that, do we have any buildbots that use *just* 2008? Or does the 2.7 compiler package from Microsoft contain the needed bits that are provided by installing Visual Studio 2010?
I think my buildslave has enough resources to support another builder for that configuration (VC9 only) if that is something we are interested in doing.
Thanks
-- Jeremy Kloth
Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
Hi David,
On Thu, Nov 3, 2016 at 2:38 PM, David Bolen <db3l.net@gmail.com> wrote:
Interesting - I probably would have assumed removing 2010 was safe for 2.7 as well. However, all of my 2.7 builders (XP/7/8/10) currently have both 2008 and 2010 so any dependency on 2010 would go unnoticed.
Assuming the 2010 dependency is unintentional, or we specifically want to test without it, the XP slave no longer builds anything but 2.7, so I could actually uninstall 2010 from that machine without affecting any other builders, or requiring any special configuration to avoid a 2010 installation.
The dependency on both 2008 and 2010 is intentional for the build files in PCbuild/. The reason is that I backported the new build files from 3.5 to allow for easier ICC support (and a few other minor benefits), but to make that work we need the compiler toolchain from 2008 and the v90 PlatformToolset files from 2010 to use with an MSBuild from 2010 or later. PC/VS9.0 is completely independent, though, and has no reliance on VS 2010.
I'd like to just add a builder to your XP bot that builds in PC/VS9.0 in addition to the regular builder in PCbuild. That will allow us to keep track of whether a change breaks one build or both. Once I have a VS9-only builder set up, if you want to remove VS2010 from any of your other bots, let me know and I'll switch its 2.7 builder to use VS9-only.
-- Zach
Zachary,
I'd like to just add a builder to your XP bot that builds in PC/VS9.0 in addition to the regular builder in PCbuild. That will allow us to keep track of whether a change breaks one build or both. Once I have a VS9-only builder set up, if you want to remove VS2010 from any of your other bots, let me know and I'll switch its 2.7 builder to use VS9-only.
The additional builder sounds fine. I don't have any particular need to remove 2010 anywhere, but wasn't sure if perhaps by having it still installed we were glossing over something on the buildslaves that a third party might run into, which doesn't seem to be the case.
In terms of switching any other builders over, I suppose the intent should be to use whatever scripts are used for the final python.org builds, so we test what will be distributed. I realize the actual compiler in use has far more ramifications than the build process, but might as well stay as aligned as possible. I'm guessing that's PCBuild, so no change to the existing builders, and the buildslaves keep the 2010 dependency for 2.7.
But for third party independent builds, it appears like the 2.7.12 documentation (https://docs.python.org/2/using/windows.html) still lists PCBuild and 2008. So perhaps that should be updated to PC/VS9.0 similar to the earlier versions? At which point, keeping at least one builder using PC/VS9.0 definitely seems like a good idea.
-- David
BTW, just to follow up on my last message:
But for third party independent builds, it appears like the 2.7.12 documentation (https://docs.python.org/2/using/windows.html) still lists PCBuild and 2008.
I should have checked first, but the readme.txt in the PCBuild directory seems to cover this in detail, so at worst, the online document is a minor issue. Although interestingly, the online doc points to PC/readme.txt which doesn't cover any of this. But I'm sure someone wanting to compile things is going to figure it out once they have the source in front of them.
And it's still probably a good idea to have a PC/VS9.0 based builder.
-- David
participants (3)
-
David Bolen -
Jeremy Kloth -
Zachary Ware