Happy Holidays, all :) There was a lot of discussion a while back about various versions of headers and libraries, and what things were included automatically during builds. I'm interested in following this but in a slightly different way. Some background: one of the things I develop are network kernel extensions (NKEs). These do not involve IOKit, which I think might be important for what follows. Until now, the NKE is a single extension which works on both 10.1.x and 10.2. There are a couple of places where it has to be sensitive to which kernel is running but I've been able to keep that fairly small. But I can see that having an appropriate extension for each kernel version (major version, at least) would be a better and safer thing and I'm heading in that direction. Obviously it would be nice to be able to build the whole product in a single build cycle. But so far it seems that you have to boot into each OS version to build the extension for that version. This blows away any notion of an automated build system, and wastes a lot of time too during development build-debug-fix cycles. So here's my question: - is there any way I can set up a development environment (I'm using ProjectBuilder for the extension) so that I can build an extension for 10.1.x using 10.1 headers etc and build the 10.2 extension using 10.2 headers, and do both while running 10.2 ?? I have a separate partition for each version already (so I can boot into whichever I need for testing etc) so all the headers etc are already available. Thanks.....Peter _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.