Chromium-如何使用mini_installer.exe制作实际的安装程序 [英] Chromium - How to make an actual installer out of mini_installer.exe

查看:324
本文介绍了Chromium-如何使用mini_installer.exe制作实际的安装程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

从源代码构建铬之后,您可以通过运行

After building chromium from source, you can create a "mini installer" for Windows by running

ninja -C out\BuildFolder mini_installer

这可以正常工作并创建 mini_installer.exe 输入 out\BuildFolder

This works fine and creates a mini_installer.exe in out\BuildFolder.

但是当我启动 mini_installer.exe 时,它只会启动铬。它无法打开一个不错的安装程序界面。

But when I launch mini_installer.exe it just launches chromium. It doesn't open a nice installer interface.

因此,我使用InnoSetup安装Chrome文件,甚至没有使用 mini_installer.exe

So instead I am using InnoSetup to install the chromium files, and I'm not even using mini_installer.exe.

有人可以描述一下这个 mini_installer应该完成的工作吗?是否可以避免我为Chromium的叉子制作自己的InnoSetup安装程序的麻烦?

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 只是一个包装以下文件的包装器:

mini_installer is just a packer which packs the following files:

 1. CHROME.PACKED.7z
 2. setup.exe

这些文件应位于您的 BuildFolder 中。 CHROME.PACKED.7z Chrome.7z ,其中包括您的Chromium文件和文件夹。

These files should be present in your BuildFolder. CHROME.PACKED.7z packs Chrome.7z which includes your Chromium files and folders.

mini_installer 会将这两个文件提取到一个临时目录中,然后执行 setup.exe 。例如,如果 mini_installer.exe 是用-系统级参数执行的,它将把这些参数传递给 setup.exe

mini_installer will extract those two files to a temporary directory and then execute setup.exe. For instance if mini_installer.exe was executed with --system-level argument, it will pass those arguments to setup.exe:

"C:\Users\Username\AppData\Local\Temp\CWB_341A7.tmp\setup.exe" --install-archive="C:\Users\Username\AppData\Local\Temp\CWB_341A7.tmp\CHROME.PACKED.7Z" --system-level

对于Chromium和Chrome,该临时文件夹名称应该不同因为我们修改了分叉以使用 CWB 前缀

That temporary folder name should be different for Chromium and Chrome cause we modified our fork to use CWB prefix

因此,它是 setup.exe 负责实际的安装和卸载过程。卸载Chromium分支时,将使用以下参数执行 setup.exe

So, it's setup.exe which is responsible for the actual installation and uninstallation process. When you uninstall your Chromium fork setup.exe will be executed with the following arguments:

 C:\Program Files (x86)\YourChromium\Application\66.0.3359.139\Installer\setup.exe --uninstall --system-level

注意:如果您通过-系统级,则将为所有用户。

Note: if you pass --system-level then it will be installed for all the users.

您传递给 mini_installer 的参数将存储在注册表中,因此相同的参数将传递给 setup.exe 卸载时。通常应将其存储在以下位置:

The arguments you pass to mini_installer will be stored in registry so the same argument will be passed to setup.exe when you uninstall it. It should typically be stored here:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\CompanyName\Update\ClientState\{Your-Chromium-fork-GUID} (for system-level installations)

<$ c的值卸载Chromium分支时,将读取并使用$ c> UninstallArguments 和 UninstallString

希望有帮助

编辑:

只要为可能觉得有用的任何人添加此信息即可。可以在此处找到安装程序的各种命令行选项:

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

这篇关于Chromium-如何使用mini_installer.exe制作实际的安装程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆