site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jun 16, 2006, at 10:59 AM, Benjamin Huntsman wrote: http://www.opendarwin.org/projects/darwinbuild/ -Jason _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I've searched all over for the answer to this before I asked, but found nothing. In some of the other open source systems I've used, one could rebuild everything, from the kernel to the user space, with just a command or two, and allow one to install the results into a separate staging directory. Also, these systems usually come with the source tree organized into some sort of hierarchy. The beauty of this is that in theory, one could cross-compile most everything on a different host. With Darwin, everything comes in packages, rather than a giant source tree. So, at Apple, what exactly does your build system look like? Are all the packages just expanded into a single directory, so that we'd have a folder for each? So, once that's set up, can one issue a single command or two to get the whole thing building? Can things be set up to build into a custom directory, or at least install there? So far, I can't even get bootstrap_cmds-49 to build without insisting that it build into /tmp/bootstrap_cmds and install over the top of my existing binaries. It even still is set up with Project Builder! Once everything is built, how does Apple find and pacakge up all the binaries into an installable form, such as the Darwin or Mac OS X distribution CD's? Lots of questions, I know, but I thought they might be helpful to some who are looking to do more than just recompile the kernel. Thanks in advance! You'll probably want to take a look at darwinbuild, if you haven't already. This email sent to site_archiver@lists.apple.com