2009/6/20 Steve Borho <st...@borho.org>
> Any InnoSetup experts out there that have experience shipping a single
> installer that supports win32 and x64 targets? I'm currently at a
> loss at how to deal with the MSVC redistributable DLLs. On the x64
> target we need the computer to have both the win32 and x64
> redistributable packages for the version of MSVC I build with (which
> as been VC8.0 for the last week). The shell extension DLL needs the
> x64 versions and python needs the win32 versions (if I build Mercurial
> with MSVC for consistency).
>
> I don't want to go back to including the redistributables in the
> installer, it would add quite a bit of bloat especially since VCS
> users usually have these libraries on their machines. My current
> thoughts on this subject are to make the installer look for the
> appropriate DLLs and not allow the install unless they are found. Do
> you all feel this would be acceptable installer behavior?
>
If it is a rare event that these DLL are missing, then it should be fine.
When aborting it would be nice if it included an URL for a location where
you could download them (or a google search term).
The other approach I'm considering is packaging the shell extension in
> it's own micro MSI installer and including both win32 and x64 versions
> in the THG installer. That would allow us to install THG as a win32
> app even on x64, and allow us to manage the DLL requirements in a
> somewhat sane fashion. As a side-benefit it provides a mechanism for
> people to use THG without the shell extension if they wish. There is
> some precedence for this, it's the exact mechanism we use for the
> win32 and x64 TortoiseOverlay packages.
I don't understand what you are proposing, but this is probably because I'm
using a 32-bit Windows.
Do you want to distribute THG as two parts?
(a) hgtk_and_everything_else_setup.exe (win32)
(b) thg_overlay_setup.exe (win32 + x64, includes tortoiseoverlay.msi,
depends on (a) )
That would be a degration for users wanting a GUI interface to hg, since
they have to run two installers.
Is it possible to make a wrapper-installer, similar to what we do with
TortoiseOverlays? Eg. a x64 installer which runs a win32 installer? From
quickly skimming the Inno Setup documentation I get the impression that the
difference between 32 and 64 bit is that the installer variables are
initialized differently. Script commands (and in particular inline
installers) does not look like they are affected.
As a Windows user I would rather download one 30 MB installer and pick which
parts I wanted to install, than download 4 installers each 8MB, and possibly
having to think about which 3 was really necessary. How should we ensure
that the correct versions of the 8MB installers are used? Is it allowed to
freely mix them?
Regards,
Peer
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Tortoisehg-discuss mailing list
Tortoisehg-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
