• I'm lazy: more steps means fewer builds, which means less testing

• Throw it in a shell script - then call that from Xcode
• Be sure to grab some kind of build identifier for your external libs and keep track of what version of them you're using - svn revision numbers are great for this
• This lets you track which version of your code is with which version of upstream code
• Put the shell script on disk, and then call it with a oneliner from the project
• this makes version control on the build script easier
• also means you can give people a link to it: http://svn.perian.org/trunk/createStaticLibs.sh
• We've got the automation to the point that you pick the Perian target, and a few minutes later you have a universal component on the other end
• "You can have a target to stick the final component in Library/QuickTime and then launch the debugger on QTPlayer. For the lazy, we can build and debug in one quick cmd-Y" -- Graham [side note: the things you learn when you have people check your presentation...]
• Next: Other Notes