Dominic Mazzoni wrote:
> On May 20, 2006, at 12:37 PM, Vaughan Johnson wrote:
>> I no longer have a VC6 installation on my machine, and can't recover
>> a fully valid one, so if we want that consistency for 1.2.5 (the
>> 1.2.x series for Windows was built with VC6), either I reinstall a
>> partial VC6 (sketchy and a bit time-consuming, although I don't think
>> any build components are missing from what I've got archived), or
>> Leland builds it because he's got VC6. I'm happy to put together the
>> installer for it from his build, if that helps. And I can build 1.3.1
>> and its installer tonight or tomorrow.
> I agree - if Leland can do the build of Audacity 1.2.5 using VC6 I
> think that would be good. Just in case there's any weird new behavior
> introduced by the newer compiler. And let's stick with Inno Setup.
> It's usually pretty easy to notice anomalies by comparing the new and
> previous versions side-by-side: the executable should grow by a small
> amount (10k-50k would be normal for a tiny point-release like this),
> the translation directory should grow by 100k-300k typically, and
> everything else should be almost identical. Any files that are
> dramatically different in size with no explanation is a warning sign.
Good points. I've found a few bugs in using Visual Studio 2005, mostly
in the resource editor (for an MFC-based project I'm working on, so
irrelevant to Audacity) and the documentation viewer (based on IE,
wouldn't you know), but the corresponding VC8 builds seem quite good.
So, I definitely think we should release 1.3.1 built on VC8, but it's
probably wise to keep 1.2.5 on VC6. Thanks, Leland!
>> Btw, I've been looking a lot at installers lately, and apropos the
>> discussion of switching to MSI files for Windows Installer, I think
>> we should *not* do so exclusively, if at all. Visual Studio 8 now
>> lets you assemble them (they have a Setup Project Wizard now), but
>> MSI files are monstrously bloated, on the order of 10 times as big as
>> InnoSetup installers, and that's the case whether the MSI files are
>> built via Visual Studio 8 or the open source Wix that Dave suggested.
> Wow! OK, let's keep Inno Setup but consider providing MSI as an
> additional option. My understanding is that MSI is most useful for
> sysadmins, as it's more useful for automatically installing something
> on a large group of computers. So perhaps we could provide an MSI and
> label it "for advanced users"?
Sounds good, but maybe the wording should be "for advanced users with
bandwidth for a ~25MB download"!
Think it's necessary for 1.2.5? Richard, can you give us some input on
how big the demand is?
I ask because it's a lot easier to make the MSI files using the Setup
Project from Visual Studio 2005 (with the VC8 builds) than to learn Wix
or the previous Microsoft stand-alone tools to apply to the VC6 build.
Previous versions of Visual Studio didn't provide Setup Projects.
Actually, if we think it's important to provide MSI files for Audacity
1.2.5, I could make a Visual Studio 2005 Setup project for it using
Leland's VC6 build -- it doesn't require executables that it built.