I haven't really kept in touch with how the installer is progressing,
but are we distributing msvc runtimes now by merging in the appropriate
microsoft redistributable installer?
In that case, it'll be necessary to put manifests in the various
pyd-files being shipped, since Python don't have that (they have it in
the main dlls). Otherwise, programs loading a different versions of the
msvc runtime can cause mercurial to fail. This can depend on what
programs you have installed on the machine, with dlls in the path.
Not sure if we already do this; in that case, disregard please :)
The manifest I put in(for python 2.6, vc2008) is:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.CRT"
version="9.0.21022.8" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
</assembly>
We just put in into all pyd files in dist, using mt.exe (resource 2),
before building the installer itself.
/Sune
------------------------------------------------------------------------------
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
