After building chromium from source, you can create a "mini installer" for Windows by running
ninja -C out\BuildFolder mini_installer
This works fine and creates a mini_installer.exe
in out\BuildFolder
.
But when I launch mini_installer.exe
it just launches chromium. It doesn't open a nice installer interface.
So instead I am using InnoSetup to install the chromium files, and I'm not even using mini_installer.exe
.
Can someone please describe what this "mini_installer" is supposed to accomplish? Can it prevent me from having to go through the trouble of making my own InnoSetup installer for my fork of Chromium?
mini_installer
is just a packer which packs the following files:These files should be present in your
BuildFolder
.CHROME.PACKED.7z
packsChrome.7z
which includes your Chromium files and folders.mini_installer
will extract those two files to a temporary directory and then executesetup.exe
. For instance ifmini_installer.exe
was executed with--system-level
argument, it will pass those arguments tosetup.exe
:That temporary folder name should be different for Chromium and Chrome cause we modified our fork to use
CWB
prefixSo, it's
setup.exe
which is responsible for the actual installation and uninstallation process. When you uninstall your Chromium forksetup.exe
will be executed with the following arguments:Note: if you pass
--system-level
then it will be installed for all the users.The arguments you pass to
mini_installer
will be stored in registry so the same argument will be passed tosetup.exe
when you uninstall it. It should typically be stored here:The value of
UninstallArguments
andUninstallString
will be read and used when uninstalling your Chromium fork.Hope that helps
EDIT:
Just adding this info for anyone who might find this useful. There are various command line options for the installer which you can find here:
chrome\installer\util\master_preferences_constants.cc