SeaMonkey:hg-based build: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
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 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 new "comm-central" Mercurial repository (test version called "calemaisu-test") 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 [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_%28Mercurial%29 getting Mozilla code via hg] and [http://developer.mozilla.org/en/docs/Mercurial Mercurial (hg) itself] from Mozilla Developer Center are probably helpful when dealing with the repositories.
The pages about [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_%28Mercurial%29 getting Mozilla code via hg] and [http://developer.mozilla.org/en/docs/Mercurial Mercurial (hg) itself] from Mozilla Developer Center are probably helpful when dealing with the repositories.
Line 23: Line 23:


* mozconfig: --enable-calendar
* mozconfig: --enable-calendar
* calendar/lightning/Makefile.in: include config.mk with the patch for {{bug|440017}}
* calendar/: apply the patch for {{bug|442566}} if it hasn't landed yet
* calendar/lightning/Makefile.in: apply the patch for {{bug|440022}} so that the produced Lighting installs well
* calendar/lightning/Makefile.in: include config.mk with the patch for {{bug|440017}} if it hasn't landed yet
* calendar/: apply the patch in http://pastebin.mozilla.org/472387 (for {{bug|442566}})
* calendar/lightning/Makefile.in: apply the patch for {{bug|440022}} (if it hasn't landed yet) so that the produced Lighting installs well

Revision as of 23:20, 2 July 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 "comm-central" Mercurial repository (test version called "calemaisu-test") 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:
 make -f client.mk build

building with Lightning calendar

  • mozconfig: --enable-calendar
  • calendar/: apply the patch for bug 442566 if it hasn't landed yet
  • calendar/lightning/Makefile.in: include config.mk with the patch for bug 440017 if it hasn't landed yet
  • calendar/lightning/Makefile.in: apply the patch for bug 440022 (if it hasn't landed yet) so that the produced Lighting installs well
Retrieved from "https://wiki.allizom.org/index.php?title=SeaMonkey:hg-based_build&oldid=98744"