[darwinbuild] Using darwinbuild for development
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/
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
I'd be willing to entertain a patch that allows for iterative building, i.e. darwinbuild -incr xnu, but as Shantonu said, that's different from the primary goal of darwinbuild. - Kevin On Sep 27, 2005, at 3:24 PM, Shantonu Sen wrote:
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
_______________________________________________ darwinbuild mailing list darwinbuild@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinbuild
Am 28.09.2005 um 03:55 schrieb Kevin Van Vechten:
I'd be willing to entertain a patch that allows for iterative building, i.e. darwinbuild -incr xnu,
Thanks for the offer. I'll look into it next time; this time it looks like I'm already finished.
On Sep 27, 2005, at 3:24 PM, Shantonu Sen wrote:
If you have all the dependencies to build xnu outside a chroot, there is no value to using darwinbuild. Why are you?
Darwinbuild's main task is to set up and maintain a correct build environment. It's just logical to use it instead of trying to follow all the dependencies manually. Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/
but you said earlier in this thread that you already had the dependencies working outside the chroot... Anyway, my point was that we can add this functionality, but it may still be slower than building outside the chroot, since we would have to duplicate source from Sources/ to BuildRoot/SourceCache, and this new functionality may interact poorly with patchfiles that modify source in BuildRoot/SourceCache Shantonu On Sep 28, 2005, at 4:03 AM, Markus Hitter wrote:
Am 28.09.2005 um 03:55 schrieb Kevin Van Vechten:
I'd be willing to entertain a patch that allows for iterative building, i.e. darwinbuild -incr xnu,
Thanks for the offer. I'll look into it next time; this time it looks like I'm already finished.
On Sep 27, 2005, at 3:24 PM, Shantonu Sen wrote:
If you have all the dependencies to build xnu outside a chroot, there is no value to using darwinbuild. Why are you?
Darwinbuild's main task is to set up and maintain a correct build environment. It's just logical to use it instead of trying to follow all the dependencies manually.
Markus
- - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/
participants (3)
-
Kevin Van Vechten
-
Markus Hitter
-
Shantonu Sen