建立svn头的好奇心（在WinXP上） [英] build curiosities of svn head (on WinXP)
问题描述
大家好！
我刚刚在winxp下使用一个相当不常见的
设置构建了版本41809（至少我认为是这样）。因为我这里没有视觉工作室，
i只使用免费提供的工具：cygwin获取源代码，
microsoft编译器/链接器和NAnt（nant.sf.net）作为构建工具
来解释.vcproj文件（这可能是不常见的部分）。
据我所知，这个设置不受支持无论如何，但是
i注意到了两个问题，这对其他人来说也很有趣。
首先，ProjectGUID'在'pythoncore'中。 vcproj"和pcbuild.sln
不匹配，我通过更改pythoncore.vcproj来修复本地
（也许视觉工作室忽略/遮蔽了这个问题？）。
秒，pcbuild.sln中的构建顺序对于elementtree似乎是错误的b $ b，nant试图在pythoncore之前构建elementtree（失败）。
i通过单独构建elementtree来修复它。
所以我的问题是：这样的东西会被改变以支持这个
设置（或者至少得到项目文件更清洁）？我应该提交
a补丁并查看它是否被接受？
除此之外一切都很顺利，我可以重现预期的
$ b回归测试套件的$ b故障（ATM）：
http://mail.python.org/pipermail/pyt...er/059033.html
顺便说一句，如果任何人都对（相当小的）构建脚本感兴趣
nant，只要问，
这么久，大卫。
hi all!
i just built revision 41809 under winxp using a rather uncommon
setup (at least i think so). since i have no visual studio here,
i only used freely available tools: cygwin to get the source, the
microsoft compiler/linker and NAnt (nant.sf.net) as the build tool
to interpret the .vcproj-files (which may be the uncommon part).
as far as i understand this setup is not supported in any way, but
i noticed two problems, that could be interesting for others as well.
first, the ProjectGUID''s in "pythoncore.vcproj" and "pcbuild.sln"
mismatch, i fixed that locally by changing "pythoncore.vcproj"
(maybe visual studio is ignoring/shadowing this problem?).
second, the build order in "pcbuild.sln" for elementtree seems to be
wrong, nant tried to build elementtree before pythoncore (which failed).
i fixed this by building elementtree separately.
so my question is: will something like this be changed to support this
setup (or at least to get the project files "cleaner")? should i submit
a patch and see if it gets accepted?
apart from that everything went fine, and i could reproduce the expected
failure (ATM) of the regression test suite:
http://mail.python.org/pipermail/pyt...er/059033.html
btw, if anyone is interested in the (rather small) build-script for
nant, just ask,
so long, David.
推荐答案
David Murmann写道：
David Murmann wrote:
大家好！
我刚刚在winxp下使用一个相当不常见的版本构建了版本41809设置（至少我是这么认为的）。因为我这里没有视觉工作室，所以我只使用免费提供的工具：cygwin获取源代码，
microsoft编译器/链接器和NAnt（nant.sf.net）作为构建工具
解释.vcproj文件（这可能是不常见的部分）。
非常好！
据我所知，这种设置不受任何支持，但是
我发现了两个问题，对其他人来说也很有趣。首先，ProjectGUID'在'pythoncore.vcproj'中。和pcbuild.sln
不匹配，我通过更改pythoncore.vcproj来修复本地化的问题
（也许视觉工作室忽略/遮蔽了这个问题？）。
那可能是。我不相信任何正在做任何认真工作的人在Windows实现中使用的是除了Visual Studio以外的任何东西（我似乎记得有些东西）副本是前一段时间捐赠的。
秒，pcbuild.sln中的构建顺序。对于elementtree似乎是错误的，nant试图在pythoncore（失败）之前构建elementtree。
我通过单独构建elementtree来修复它。
是的，elementtree模块是一个3.5的新到货，所以构建可能还没有完美指定
。这是有用的信息。
所以我的问题是：这样的东西会被改变以支持这个设置（或至少让项目文件更干净）？我应该提交一个补丁，看看它是否被接受了？
我怀疑补丁被接受的机会要高得多，如果
作者将致力于为其提供持续的支持。目前开发人员似乎觉得这是唯一一种可靠的方式来支持
合并一个新平台（有人最近宣布他们有一个
工作DOS的2.4实现，但是由于对
持续支持的怀疑而对
有一些阻力，包括它作为构建的标准部分。）
除此之外一切都很顺利，我可以重现回归测试套件的预期失败（ATM）：
http://mail.python.org/pipermail/pyt...er/059033.html
顺便说一下，如果有人对（相当小的）构建脚本感兴趣，请问，
这么久，大卫。
hi all!
i just built revision 41809 under winxp using a rather uncommon
setup (at least i think so). since i have no visual studio here,
i only used freely available tools: cygwin to get the source, the
microsoft compiler/linker and NAnt (nant.sf.net) as the build tool
to interpret the .vcproj-files (which may be the uncommon part).
Excellent!
as far as i understand this setup is not supported in any way, but
i noticed two problems, that could be interesting for others as well.
first, the ProjectGUID''s in "pythoncore.vcproj" and "pcbuild.sln"
mismatch, i fixed that locally by changing "pythoncore.vcproj"
(maybe visual studio is ignoring/shadowing this problem?).
That could be. I don''t believe anyone who''s doing any serious work on
the Windows implementation is using anything other than Visual Studio (I
seem to remember that a few copies were donated a while ago).
second, the build order in "pcbuild.sln" for elementtree seems to be
wrong, nant tried to build elementtree before pythoncore (which failed).
i fixed this by building elementtree separately.
Yes, the elementtree module is a new arrival for 3.5, so the build may
not yet be perfectly specified. This is useful information.
so my question is: will something like this be changed to support this
setup (or at least to get the project files "cleaner")? should i submit
a patch and see if it gets accepted?
I suspect that the patch''s chances of being accepted are much higher if
its author will commit to providing ongoing support for it. At present
the developers seem to feel that this is the only reliable way to
incorporate a new platform (someone recently announced they had a
working DOS implementation of 2.4, but there was some resistance to
including it as a standard part of the build because of doubts about
ongoing support).
apart from that everything went fine, and i could reproduce the expected
failure (ATM) of the regression test suite:
http://mail.python.org/pipermail/pyt...er/059033.html
btw, if anyone is interested in the (rather small) build-script for
nant, just ask,
so long, David.
这是个好消息。就在最近有迹象表明，Windows平台需要更大的开发人员基础，这可能只是促进这一点的事情。可能值得快速发布
python-dev以了解您的新开发项目对您有何兴趣。做得好！
问候
Steve
-
Steve Holden +44 150 684 7255 +1 800 494 3119
Holden Web LLC www.holdenweb.com
PyCon TX 2006 www.python.org/pycon/
This is terrific news. Just recently there have been indications that
the Windows platform needs a larger base of developers, and this might
be just the thing to promote that. It might be worth a quick post to
python-dev to see what interest your new development gets. Well done!
regards
Steve
--
Steve Holden +44 150 684 7255 +1 800 494 3119
Holden Web LLC www.holdenweb.com
PyCon TX 2006 www.python.org/pycon/
Steve Holden写道：
Steve Holden wrote:
David Murmann写道
David Murmann wrote
[ ...]
[...]
除此之外一切都很顺利，我可以重现回归测试套件的预期失败（ATM）：
http：// mail .python.org / pipermail / pyt ... er / 059033.html
顺便说一下，如果有人对
na的（相当小的）构建脚本感兴趣嗯，请问，
这么久，大卫。
apart from that everything went fine, and i could reproduce the expected
failure (ATM) of the regression test suite:
http://mail.python.org/pipermail/pyt...er/059033.html
btw, if anyone is interested in the (rather small) build-script for
nant, just ask,
so long, David.
这是个好消息。就在最近，有迹象表明Windows平台需要更多的开发人员，这可能只是促进这一点的事情。可能值得快速发布
python-dev以了解您的新开发项目的兴趣。干得好！
This is terrific news. Just recently there have been indications that
the Windows platform needs a larger base of developers, and this might
be just the thing to promote that. It might be worth a quick post to
python-dev to see what interest your new development gets. Well done!
David：
显然Tim Peters刚刚找到了构建原因
错误使用VC7，所以Subversion存储库现在应该持有一个有效的
项目文件供你测试。
问候
史蒂夫
-
Steve Holden +44 150 684 7255 +1 800 494 3119
Holden Web LLC www.holdenweb.com
PyCon TX 2006 www.python.org/pycon/
David:
Apparently Tim Peters has just tracked down the causes of the build
errors with VC7, so the Subversion repository should now hold a valid
project file for you to test against.
regards
Steve
--
Steve Holden +44 150 684 7255 +1 800 494 3119
Holden Web LLC www.holdenweb.com
PyCon TX 2006 www.python.org/pycon/
[David Murmann ]
....
[David Murmann]
....
第二，pcbuild.sln中的构建顺序对于elementtree似乎是错误的，nant试图在pythoncore（失败）之前构建elementtree。
我通过单独构建elementtree来修复它。
[Steve Holden]
second, the build order in "pcbuild.sln" for elementtree seems to be
wrong, nant tried to build elementtree before pythoncore (which failed).
i fixed this by building elementtree separately.
[Steve Holden]
是的，elementtree模块是3.5的新到货，因此构建可能尚未完全指定。这是有用的信息。
Yes, the elementtree module is a new arrival for 3.5, so the build may
not yet be perfectly specified. This is useful information.
我刚刚检查了修复程序。谢谢！
....
...我可以重现回归测试套件的预期故障（ATM）：< >
请注意，所有测试都在Windows上传递为星期日（发布和调试
版本，有和没有-O）。
Note that all tests pass on Windows as of Sunday (in release and debug
builds, with and without -O).
这篇关于建立svn头的好奇心（在WinXP上）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
