[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TortoiseOverlay merge module questions

From: Adrian Buehlmann <adrian_at_cadifra.com>
Date: Mon, 01 Mar 2010 02:44:16 +0100

On 26.02.2010 19:47, Stefan Küng wrote:
> On 26.02.2010 10:54, Adrian Buehlmann wrote:
>>> Also, what you call a "functional msi" might work on your system with
>>> your specific version of the windows installer. Someone using another
>>> version of the windows installer might get another result or the
>>> installation won't work at all.
>> We will ship exactly that in TortoiseHg 1.0, in a couple of days
>> (an msi having both 32 and 64 bit components).
>> But of course without the TortoiseOverlays x86 in our x64 installer, due to
>> the component GUID conflict. We will request our users to download and install
>> TortoiseOveralys x86 themselves for x64 platforms if they want to have
>> overlay icons in 32 bit processes (tested, works fine, but of course is
>> clumsy), citing the GUID conflict.
>> I admit I haven't tested yet on Win XP x64 but on clean Vista x64 SP2 and
>> Windows 7 x64 all this works fine.
> I wouldn't be so sure about that. Do an install but with a full log. You
> might be surprised about what doesn't work.
> Please read this post about the problems:
> http://blogs.msdn.com/heaths/archive/2008/01/15/different-packages-are-required-for-different-processor-architectures.aspx

Rereading that blog post a few more times, I think the blogger is just
telling us, that we need a 64-bit package to install on 64-bit platforms
and a separate 32-bit package to install on 32-bit platforms.

That's what we do.

We do even forbid the 32-bit installer to run, if it it is started on a
64-bit platform. The 64-bit installer will implicitly produce an error
if it is started on a 32-bit platform.

*But* I fail to see where that blog post says that we cannot have both
64-bit and 32-bit components in the 64-bit package. I say we can, and
that's what we do on TortoiseHg.

We don't have any 64-bit components in our 32-bit installer package.

I also don't see any of those bad "will substitute" in our 64-bit logs,
but I see both "BinaryType=0" and "BinaryType=1", also for registry
setting "Executing op"s. From which I conclude that the 64-bit installer
is actually writing to both the 32-bit and the 64-bit areas of the registry.

BTW, the only 64-bit component TortoiseHg itself has is ThgShellx64.dll,
which is installed in "C:\Program Files\Common Files\TortoiseHg".
Everything else (dialogs, hg.exe, etc.) is 32-bit (in both installers)
and is installed in "C:\Program Files (x86)\TortoiseHg" (including our
32-bit shell extension "ThgShellx86.dll").


To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-01 10:58:51 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.