On 19.02.2010 19:18, Sune Foldager wrote: > On 19-02-2010 18:43, Steve Borho wrote: >> On Fri, Feb 19, 2010 at 11:37 AM, Sune Foldager <sune.folda...@me.com> wrote: >>> On 19-02-2010 17:04, Steve Borho wrote: >>> >>>> Someone should double-check, but I could swear I see the mt tool >>>> running on the Mercurial C extensions when we compile them with >>>> thg-winbuild. I suppose it's trivial to check after the fact. >>> >>> Yes it does, but there aren't manifests in the pyd files shipping with >>> Python, such as win32event.pyd etc. This is on purpose to enable >>> side-by-side shipping of executables, amusingly enough :-p. >> >> I've been digging around in our library.zip file, and the only pyds I >> could find without manifests were the PyGtk libraries, and they >> require the same version of msvcrt that we ship (by pure luck). > > Not pure luck; all 2.6 modules require 9.0 msvcrt. Even so, you can run > into trouble if a file manager, say, which uses an older version of > msvcrt, loads the TortoiseHg extension. This is how we discovered it in > the first place. Manifests make sure the correct version is loaded. > > See also http://bugs.python.org/issue4120 > > None of the python-shipped (at least python.org 2.6 package) pyd-files > have manifests.
Sune told me on irc that by "TortoiseHg extension" he means the Windows shell extension (was the first time I saw someone using that term, so I had to ask :). TortoiseHg's shell extension is statically linked. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
