SeaMonkey:hg-based build: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (%s/autoconfig/autoconf/)
Line 15: Line 15:
* check if the supplementary patch for {{bug|440932}} has landed, else apply it manually in mozilla/
* check if the supplementary patch for {{bug|440932}} has landed, else apply it manually in mozilla/
* if you're on Windows, check if the patch for {{bug|442503}} has landed, else apply it manually in mozilla/
* if you're on Windows, check if the patch for {{bug|442503}} has landed, else apply it manually in mozilla/
* make sure you have autoconfig 2.13 installed, see [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_%28Mercurial%29#Autoconf_2.13 the comment about this on MDC]
* make sure you have autoconf 2.13 installed, see [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_%28Mercurial%29#Autoconf_2.13 the comment about this on MDC]
* create a mozconfig, using the normal --enable-application=suite (for SeaMonkey, mail for Thunderbird)
* create a mozconfig, using the normal --enable-application=suite (for SeaMonkey, mail for Thunderbird)
* build using client.mk:
* build using client.mk:

Revision as of 12:51, 29 June 2008

The work for building SeaMonkey and Thunderbird with mozilla-central has originally been based on the SeaMonkey/1.9.1_Repository_Options, and then refined following MailNews:HgMeetingNotes to use it own testing repository.

The new yet-to-be-named Mercurial repository contains SeaMonkey and Thunderbird code for now, calendar will follow at a later date. All of those codebases are imported as static snapshots from CVS, without keeping history, which will be available through cvs and web tools. The shared repository contains its own build system files, which started off as copies of the Mozilla equivalents, with some path adjustments and removals of not needed parts. For now, they call into lots of mozilla files, which can be gradually reduced over time so that in the end SeaMonkey and Thunderbird can build with some sort of a XULRunner SDK.

The pages about getting Mozilla code via hg and Mercurial (hg) itself from Mozilla Developer Center are probably helpful when dealing with the repositories.

building SeaMonkey or Thunderbird

 hg clone http://hg.mozilla.org/users/kairo_kairo.at/calemaisu-test/ src
 cd src
  • update/pull all other needed source via client.py
 python client.py checkout
  • check if the patch for bug 442484 has landed, else apply it manually in mozilla/ (note that with hg, all patches need to applied with at least -p1 level in patch!)
  • check if the supplementary patch for bug 440932 has landed, else apply it manually in mozilla/
  • if you're on Windows, check if the patch for bug 442503 has landed, else apply it manually in mozilla/
  • make sure you have autoconf 2.13 installed, see the comment about this on MDC
  • create a mozconfig, using the normal --enable-application=suite (for SeaMonkey, mail for Thunderbird)
  • build using client.mk:
 gmake -f client.mk build

building with Lightning calendar

This section is OUTDATED and will be replaced with more current information later.

  • pull from CVS: mozilla/calendar/
  • pull from CVS: mozilla/extensions/lightning/
  • pull from CVS: mozilla/extensions/webdav/
  • mozconfig: --enable-extensions=default,lightning
  • mozilla/calendar/lightning/Makefile.in: include config.mk with the patch for bug 440017
  • suite/app-config.mk and mail/app-config.mk: add the following lines at the end of the file:
# needed to install the Lightning extension if it's built
INSTALL_LIGHTNING = 1
  • mozilla/calendar/lightning/install.rdf: apply the patch for bug 440022 so that the produced Lighting installs well.