Is there a way to build an offline installer for Chromium?

[John Miller]

Hello,

Is there a way to build an offline installer for Chromium like the ones for Chrome provided here:
http://support.google.com/installer/bin/answer.py?hl=en&answer=126299

I see a setup project in the repository, but it clearly uses the GoogleUpdate mechanisms.
Are the scripts for packaging Chrome for offline installation present in some other private repository?

[Robert Shield]

This is Windows-specific, I don't know how things work for other platforms:

The standalone installer you linked to is the Google Update installer packaged with Chrome's mini_installer.exe. 

mini_installer is a target in the Chromium repo, you should be able to build that directly and it can be used to install a non-updating Chromium.

If you want an offline installer that also includes the client part of an update service (similar to the one you linked to), then the code for Google Update can be found here: https://code.google.com/p/omaha. You would have to roll your own update server.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
 
 
 

[John Miller]

Thanks Robert,

The problem was that I was looking in the src\chrome\chrome.sln solution, instead of the correct src\chrome\installer\mini_installer.sln (which also features everything necessary to build Chromium).
My next problem is that I don't see any provisions for code signing in the gyp files or in create_installer_archive.py on WIndows. Am I missing something again? (on Mac, these seems to be a file called sign_app_sh.in responsible for this).

[Robert Shield]

On Mon, Mar 18, 2013 at 7:44 AM, John Miller <zah...@gmail.com> wrote:

Thanks Robert,

The problem was that I was looking in the src\chrome\chrome.sln solution, instead of the correct src\chrome\installer\mini_installer.sln (which also features everything necessary to build Chromium).
My next problem is that I don't see any provisions for code signing in the gyp files or in create_installer_archive.py on WIndows. Am I missing something again? (on Mac, these seems to be a file called sign_app_sh.in responsible for this).

The code signing build scripts for Google Chrome are in a different place and (for Windows at least) aren't included in the chromium repo. They aren't anything particularly complicated, (they just run signtool.exe on the bits we want to sign from the output of the mini_installer build), but you'll have to roll your own signing build step if this is something you'd like to do.

[Zahary Karadjov]

Thanks for the clarification.

I had to modify create_installer_archive.py a little bit to sign the main executable in the staging dir,
before the 7Z file is created and embedded inside mini_installer, but that was easy to do.