If you have all the dependencies to build xnu outside a chroot, there is no value to using darwinbuild. Why are you? darwinbuild emulates Apple's build system, which cleans out old object files between builds. Many projects don't do correct dependency tracking, or fail when old intermediates are present. The point of darwinbuild is to be reproducible and self-contained, and is not the best option for iterative development if you already have that working. Shantonu On Sep 27, 2005, at 3:18 PM, Markus Hitter wrote:
Hello all,
a few days ago I decided to give the kernel a kick. As there are so many good comments about darwinbuild, I set up this to build the thing.
Now, it seems a lot like the kernel is built from scratch each time I issue darwinbuild, regardless of how much code I change. Even two "darwinbuild xnu" in a row do two full rebuilds each time. In comparison, building xnu outside darwinbuild makes builds after a small code change almost a snap (5 min vs. 40 min).
Is there something I could do about this?
Thanks, Markus
- - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/
_______________________________________________ darwinbuild mailing list darwinbuild@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinbuild