Creating release build of Omaha

Here is the command to build release version of Omaha client:

hammer --mode=opt-win --build_server --authenticode_file=<path_to_pfx_file>.pfx --authenticode_password=<certificate_password> --patching_certificate=<path_to_cer_file>.cer

The meaning of command line parameters:

• --mode=opt-win tells to build optimized version, i.e. the version without debug information
• --build_server switch marks the build as "official"
• --authenticode_file is the Personal Information Exchange (PFX) file containing the certificate
• --authenticode_password is the password to use when opening a PFX file
• --patching_certificate is the certificate itself

authenticode_file and authenticode_password are used by the normal signing tool and to sign manifests for ClickOnce and patching_certificate is used to create patchable MSI installers and MSPs.

Before signing with custom certificate, one must change the kCertificateSubjectName constant in base\constants.h to match the company and organization names expected in Authenticode certificates.