130
edits
Mobile/Build/Windows Mobile Build Instructions: Difference between revisions
Mobile/Build/Windows Mobile Build Instructions (view source)
Revision as of 03:51, 27 November 2008
, 27 November 2008→Downloading and Building
MarkFinkle (talk | contribs) No edit summary |
|||
| Line 121: | Line 121: | ||
$ '''export PATH="$PATH:$topsrcdir/build/wince/tools/bin"''' | $ '''export PATH="$PATH:$topsrcdir/build/wince/tools/bin"''' | ||
===CRUD - The Clone of Mozilla-Central Freezes=== | |||
Several people have reported that the cloning of mozilla-central as described above freezes and does not complete. | |||
If your clone of mozilla-central is taking more than an hour to complete, you may be in this same situation. Basically, this can be caused by a number of different situations: | |||
* The Mozilla hg repository is overloaded, | |||
* The Internet Connection you have is very slow and times out | |||
* The Internet Connection you have drops enough packets that HG gets confused | |||
As a point of reference, John Wolfe has a very fast RCN cable modem connection at home. However, he found out a while ago that RCN considers a 7% data loss to be within acceptable limits for customer service. 7% Data Loss (tested via pinging from an internal-to-RCN server to John Wolfe's cable modem) means that 7 out of every 100 packets gets ''lost''' within the RCN internal network. | |||
This means that when RCN gets busy (nights and weekends, for instance), it is almost guaranteed that John Wolfe will not be able to do a full HG clone operation on the mozilla-central repository. | |||
Here is what you can do to get around HG freezing when cloning mozilla-central: | |||
# Download the [http://hg.mozilla.org/mozilla-central/archive/tip.tar.bz2 latest tip of mozilla-central (in TAR BZ2 form)] | |||
# Create a new, empty mozilla-central repository: | |||
$ '''cd /c/hg''' | |||
$ '''hg init mozilla-central''' | |||
# Un-bundle the real mozilla-central changes to that repository: | |||
$ '''cd mozilla-central;''' | |||
$ '''hg unbundle /path/to/mozilla-central.bundle/tip.tar.bz2''' | |||
# Tell mercurial where you normally want to pull from by copying the | |||
following content into your mozilla-central/.hg/hgrc file: | |||
[paths] | |||
default = http://hg.mozilla.org/mozilla-central/ | |||
# Pull any changes that happened since the bundle was created: | |||
$ '''hg pull''' | |||
# Update your working directory to the latest change: | |||
$ '''hg update''' | |||
NOTE: You will want to do two seperate operations for pulling then updating, as some versions of HG have a bug in their ''hg pull -u'' command. I forget exactly what the bug is - but the work-around is to do these two seperate operations. | |||
Thanks go out to Benjamin Smedbergs for this solution - [http://benjamin.smedbergs.us/blog/2008-06-05/getting-mozilla-central-with-limited-bandwidth/ Original Blog Posting Here] | |||
| Line 172: | Line 214: | ||
$ '''make -f client.mk build''' | $ '''make -f client.mk build''' | ||
==Notes After Building== | ==Notes After Building== | ||