canmove, Confirmed users
6,439
edits
ReferencePlatforms/Mac: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
= | = Darwin Version = | ||
These are the kernel versions we're starting with: | These are the kernel versions we're starting with: | ||
| Line 12: | Line 10: | ||
Intel: Darwin bm-xserve08.build.mozilla.org 8.8.4 Darwin Kernel Version 8.8.4: Sun Oct 29 15:26:54 PST 2006; root:xnu-792.16.4.obj~1/RELEASE_I386 i386 i386 | Intel: Darwin bm-xserve08.build.mozilla.org 8.8.4 Darwin Kernel Version 8.8.4: Sun Oct 29 15:26:54 PST 2006; root:xnu-792.16.4.obj~1/RELEASE_I386 i386 i386 | ||
= Initial Setup and Account Creation = | |||
# Change the resolution to 1024 x 768, 60 Hz, under System Preferences->Displays. | # Change the resolution to 1024 x 768, 60 Hz, under System Preferences->Displays. | ||
| Line 22: | Line 20: | ||
# Using the Workgroup Manager, open the Preferences pane for the cltbld user. Under Software Update, set Manage: to Always, and set the Software Update server to use: as http://bm-xserve01.build.mozilla.org:8088/ | # Using the Workgroup Manager, open the Preferences pane for the cltbld user. Under Software Update, set Manage: to Always, and set the Software Update server to use: as http://bm-xserve01.build.mozilla.org:8088/ | ||
= ssh = | |||
The first step is to get ssh working with the cltbld keys on the new machine. Unfortunately, this presents a bit of a chicken-and-egg problem, as the ssh keys necessary to access cvs are not yet on the machine. | The first step is to get ssh working with the cltbld keys on the new machine. Unfortunately, this presents a bit of a chicken-and-egg problem, as the ssh keys necessary to access cvs are not yet on the machine. | ||
| Line 30: | Line 28: | ||
# scp the cltbld keys over directly from a machine that already has them installed (<code>cd ~;scp -r xserve06:~/.ssh .</code>) | # scp the cltbld keys over directly from a machine that already has them installed (<code>cd ~;scp -r xserve06:~/.ssh .</code>) | ||
= ENV setup = | |||
ocvs -d :ext:cltbld@cvs.mozilla.org:/mofo co release/tinderbox-configs/host | ocvs -d :ext:cltbld@cvs.mozilla.org:/mofo co release/tinderbox-configs/host | ||
| Line 37: | Line 35: | ||
...at which point you'll probably want to restart your shell to use the new .profile. | ...at which point you'll probably want to restart your shell to use the new .profile. | ||
= Ref platform packages = | |||
The next step is to retrieve the Mac reference platform packages from CVS: | The next step is to retrieve the Mac reference platform packages from CVS: | ||
| Line 51: | Line 49: | ||
3f02477e0df2a3bc53d02fe0824c0015 chud_4.5.0.dmg | 3f02477e0df2a3bc53d02fe0824c0015 chud_4.5.0.dmg | ||
= Installing Xcode = | |||
# Mount the Xcode disk image, and begin installing the XcodeTools.mpkg. | # Mount the Xcode disk image, and begin installing the XcodeTools.mpkg. | ||
| Line 57: | Line 55: | ||
# Under "Cross-Development," select all the available SDKs, and then click "Install" | # Under "Cross-Development," select all the available SDKs, and then click "Install" | ||
= Installing CHUD = | |||
# Mount the CHUD disk image, install the CHUD.mpkg | # Mount the CHUD disk image, install the CHUD.mpkg | ||
= Installing DarwinPorts = | |||
* Install the DarwinPorts package from ref platform version 1.3.1-10.4 | * Install the DarwinPorts package from ref platform version 1.3.1-10.4 | ||
| Line 97: | Line 95: | ||
Running <code>port installed</code> after you're done should show only the 15 ports listed above as installed. | Running <code>port installed</code> after you're done should show only the 15 ports listed above as installed. | ||
= Installing SharedMenusCocoa = | |||
# Open the SharedMenusCocoa image. | # Open the SharedMenusCocoa image. | ||
| Line 103: | Line 101: | ||
# Follow [http://wiki.caminobrowser.org/Development:Building the instructions on the Camino build reference page] for creating the links in the older SDKs. If you are building on an Intel Mac or need to build a Universal Camino, you will also need to follow the instructions for recompiling a UB version of the framework. NOTE: make sure you have the SharedMenusCocoa.framework linked under <em>ALL</em> your SDKs (including 10.4) just to be safe. | # Follow [http://wiki.caminobrowser.org/Development:Building the instructions on the Camino build reference page] for creating the links in the older SDKs. If you are building on an Intel Mac or need to build a Universal Camino, you will also need to follow the instructions for recompiling a UB version of the framework. NOTE: make sure you have the SharedMenusCocoa.framework linked under <em>ALL</em> your SDKs (including 10.4) just to be safe. | ||
= chown scripts = | |||
After you've created your initial /builds/tinderbox directory structure, checkout and build the following tools that are also required for changing permissions while packaging on Macs: | After you've created your initial /builds/tinderbox directory structure, checkout and build the following tools that are also required for changing permissions while packaging on Macs: | ||
| Line 119: | Line 117: | ||
ln -s chown_revert revert_root | ln -s chown_revert revert_root | ||
= Establish initial ssh connections and accept keys = | |||
You'll need to execute the following simple ssh calls to connect to the ftp server (stage), symbol server, and update server so that the various pieces of the build can be uploaded automatically by the build scripts when needed: | You'll need to execute the following simple ssh calls to connect to the ftp server (stage), symbol server, and update server so that the various pieces of the build can be uploaded automatically by the build scripts when needed: | ||
| Line 127: | Line 125: | ||
ssh -i /Users/cltbld/.ssh/aus cltbld@aus2-staging.mozilla.org pwd | ssh -i /Users/cltbld/.ssh/aus cltbld@aus2-staging.mozilla.org pwd | ||
= Mail config = | |||
You'll need to update the postfix config to make sure that <code>myhostname</code> is set correctly and that large messages can be sent. The tail of <code>/etc/postfix/main.cf</code> should look similar to: | You'll need to update the postfix config to make sure that <code>myhostname</code> is set correctly and that large messages can be sent. The tail of <code>/etc/postfix/main.cf</code> should look similar to: | ||