Small cross-platform software update installer
Find a file
Robert Knight 04c9c7204b Make updater.exe a WIN32 GUI application instead of a console application on Windows
* Add WIN32 flag to add_executable() so that cmake generates a GUI application
 * Add WinMain() entry point which converts the unicode command line arguments to ANSI and then calls the standard main() entry point.

 The unit test continues to pass although I am not sure whether
 converting command-line args from Unicode to ANSI will cause problems
 with filenames passed on the command-line that contain non-ANSI
 characters.
2011-08-24 16:11:53 +01:00
external Add pre-built zlib library to build tree for Windows builds 2011-08-23 20:38:20 +01:00
src Make updater.exe a WIN32 GUI application instead of a console application on Windows 2011-08-24 16:11:53 +01:00
CMakeLists.txt Merge branch 'master' of ssh://gitweb/git/desktop/standalone-updater 2011-08-24 10:46:17 +01:00
README Improve the description of the tool in the README file 2011-08-21 22:27:10 +01:00
TODO Update TODO file 2011-08-24 12:29:43 +01:00

This tool is a component of an auto-update system.  It is responsible for performing
the installation of an update after the necessary files have been downloaded
to a temporary directory.

This tool is responsible for:

 * Reading an XML file specifying the contents of an update.
 
 * Extracting and installing updated files from one or more compressed packages.
   
 * Removing any files which are no longer needed in the new version of the application.

 * Requesting elevated priviledges if required to install the update.

 * Displaying a simple updater UI and re-launching the main application
   once the update is installed.

The tool consists of a single small binary which only has a small number of external 
dependencies that need to be present on the target system.

The external dependencies of the updater binary are:

 * The C++ runtime library (Linux, Mac),
 * pthreads (Linux, Mac),
 * zlib (Linux, Mac)
 * native UI library (Win32 API on Windows, Cocoa on Mac).

To perform an update, the application (or another separate tool) needs to download
the updater binary, an XML file describing the update and one or more zip packages
containing the files for the update to a temporary directory.  It then needs
to invoke the updater, specifying the installation directory, temporary package
directory and path to the update script file.  The updater then installs the
update and restarts the application when done.