130
edits
Mobile/Build/Windows Mobile PrepForBuild: Difference between revisions
Jump to navigation
Jump to search
Mobile/Build/Windows Mobile PrepForBuild (view source)
Revision as of 00:53, 20 February 2009
, 20 February 2009→Turn On Mercurial Patch Queue Extension
(New page: =Preparing To Build XULRunner and Fennec For Windows Mobile= Here is a big-picture view of the steps needed to prepare a new PC for building the Windows Mobile Fennec and/or a Windows Mob...) |
|||
| Line 81: | Line 81: | ||
[http://hgbook.red-bean.com/hgbookch12.html#x16-26700012 Turn on the mercurial queues extension]. | [http://hgbook.red-bean.com/hgbookch12.html#x16-26700012 Turn on the mercurial queues extension]. | ||
Summary: Because Mercurial Patch Queues (MQ) is implemented as an extension, you must explicitly enable before you can use it. You don’t need to download anything; MQ ships with the standard Mercurial distribution. | |||
This can be accomplished by adding a .hgrc file to your home directory. | |||
You can find your home directory by running the c:\mozilla-build\start-msvc9.bat (or start-msvc8.bat) batch file, and issuing these commands: | |||
$ cd ~ | |||
$ pwd | |||
Your home directory is also set into an environment variable $HOME. | |||
To find your home directory you could also issue the command | |||
$ echo $HOME | |||
The contents of your .hgrc file should be as follows: | |||
[ui] | |||
username = '''Your Real Name <user@example.com>''' | |||
merge = internal:merge | |||
[extensions] | |||
hgext.mq = | |||
[defaults] | |||
commit = -v | |||
[diff] | |||
git = 1 | |||
showfunc = 1 | |||
unified = 8 | |||
This $HOME\.hgrc (or $HOME\Mercurial.ini) file does several things: | |||
(1) Sets up your username for Mercurial | |||
(2) Sets up your merge to use the Mercurial built-in merge | |||
(3) Gives verbose information on any HG COMMIT operations you do | |||
(4) Sets the DIFF options to be GIT unified format, with 8 lines of context, and each block lists the function name closest to the modification spot. | |||
This is a very strongly suggested practice for developing in the Mozilla ecosphere. | |||
Mercurial patch queues make it very easy to try out changes, save the changes in a series of patches, then remove and/or apply those changes quickly. | |||
While the learning curve can be tough on both Mercurial and Mercurial Patch Queues, the tools do help development by distributing repository control. | |||
==OPTIONAL Download and Install Latest Mercurial== | ==OPTIONAL Download and Install Latest Mercurial== | ||