- #TINDERBOX MAC OS X SYSTEM REQUIREMENTS HOW TO#
- #TINDERBOX MAC OS X SYSTEM REQUIREMENTS INSTALL#
- #TINDERBOX MAC OS X SYSTEM REQUIREMENTS UPGRADE#
I know I don't have a download of these packages I'll see if IT does.
#TINDERBOX MAC OS X SYSTEM REQUIREMENTS INSTALL#
This means doing a custom install of Xcode and selecting all SDKs. When installing Xcode, we need to make sure that all SDKs get You can download these from if you have a free > We need to use Xcode 2.2.1 on all Tiger machines, and Xcode 1.5 on all 10.3.9 Great so do can you add to the list which machines are currently responsible for which builds? > I don't know of any reason that the roles need to change. Chase had a very standard way of setting up tbox configs, I don't know what that is and I've never successfully set up a tinderbox myself. Then someone can set up the tinderbox however they like and it should build just fine. I can do that quickly, and I do it all the time so we can avoid having to debug problems. Then I will install Xcode and darwinports, set up a build environment. I envision this working in 3 steps - someone wipes the machine and puts the target OS version on it, then sets up ssh and VNC. An example would be that we suspect there is something wrong with the toolchain on at least one of the Camino tinderboxes (something funny with "make"?). A clean slate will assure us of a standard, conflict-free build environment. I don't like the idea of inheriting any "interesting" setups for our build environment when I'm not aware of any need for anything special. Better check anyway though, as dbaron suggested.Īlso, it would be comforting to me to know exactly what tools are on the machine and how they are set up. Which I doubt because Chase was able to set up tinderboxes in about 3-5 minutes and never mentioned anything special that had to be done to me.
#TINDERBOX MAC OS X SYSTEM REQUIREMENTS UPGRADE#
I don't think it is worth the risk, and I doubt it will be faster to upgrade than it will be to just start clean unless there is something crazy going on with tbox configs. We're going to have to go through that twice for any machines we want to move from 10.2 to 10.4 (many of them). Especially if you're messing around in the BSD subsystem with Terminal, doing things like installing fink and changing permissions. The reason I suggest doing this is that there is a higher risk of something going wrong when you upgrade major OS version. See the bug summary about this.Įrase and install erases the whole disk, not just the OS. This means doing a custom install of Xcode and selecting all SDKs.įor package management (libidl, that kind of thing) we should be using darwinports. When installing Xcode, we need to make sure that all SDKs get installed. You can download these from if you have a free account there.
We need to use Xcode 2.2.1 on all Tiger machines, and Xcode 1.5 on all 10.3.9 machines.
#TINDERBOX MAC OS X SYSTEM REQUIREMENTS HOW TO#
> needed,how/where to get them, and (if it's non-obvious) how to install them? Could you include a list of the necessary compilers/ tools that are I don't know of any reason that the roles need to change. > products they'll build on which branches?) Maybe they won't change? Could you put what each machine's expected role is going to be (which