A script that can be called by VS to build the currently selected build type in VS into an installer than can be distributed. Should support bundling up debug builds as well so that mod authors have something to test with.

The installer should offer the option to disable news retrieval (for the initial release) and updates check (for the second release) during the setup process.

Comment deleted

Revision 2fd3a8aaf2
Everything in the output directory for the specified build type should be all that is required for the launcher to work.

Comment deleted

Comment #1 invalidated by Issue 31 http://code.google.com/p/wxlauncher/issues/detail?id=31

The option to disable internet connectivity will be offered by the launcher itself in order to make it cross-platform.

Changed owner to Iss Mneur due to the move to the CMAKE build system.

Before creating the NSIS script we need to know how to implement it.

Issue remains open.

What sort of modifications to the NSIS script that CMake generates are we looking to implement.

At the first glance, this is what we should be able to change in the installer:

• icon
• top banner
• welcome banner
• checkboxes to open the readme file and launch the launcher when the the installation (we need to have a readme file packed in the installer that contains at least the dependencies required by the launcher, a quick overview of the launcher and a quickstart guide - the detailed guide will be in the help file)
• (misc) change the installer "Nullsoft install system v x.xx" or similar text displayed by the installer.

There is no need to have a "Chose components" installer page since the only optional components will be the language packs (if we'll add them to the install package) and I suppose the language packs will be pretty lightweight compared to the launcher itself. There is no need to integrate the 2008 runtimes in the install package also. Having the link in the readme file will be enough. This will result in smaller installer too.

Okay, will work on exposing these features.

I disagree about the runtimes though, I think the installer should install them, because we do not want users to have to read the readme. Though if installer size is a concern, we could always have the installer check to see if the VS2008 SP1 runtimes have been installed and if not have the installer download and install them.

Yeah, you're right about the runtimes.

The quickest and safest solution is to include them in the installer. This will work for offline installations too.

The professional solution is to have the installer download them. Obviously, this will require internet access.