We're starting to port a kernel module to Mac OS X that has

been previously

ported to several UNIX platforms and Windows. For _all_

platforms we use

make to build the software and packaging, which makes it much easier

for different developers (who are located in different

countries etc) on

different

platforms to make changes/reorganise etc, especially when none of the

developers have direct acceess to build machines for all platforms.

We have the exact same situation. We tackled it in several different ways as we gained some experience with OS X: 1) Use Project Builder, then copy and paste the compile and link commands it uses from its log. 2) Recognize that PB uses Jam, and create your own calls to Jam, which in turn calls the compile and link commands. We left the organization of resources, such as .pbx and .plist files, alone so that we may continue to use PB if desired. We also added some niceties into our makefiles to edit the .plist files at compile time to keep the KEXT's version numbers up-to-date. Hope this helps. Cory Stockhoff cstoc@netlock.com _______________________________________________ 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.