site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com When developing for VFS on Mac OS X, start here. <http://developer.apple.com/qa/qa2001/qa1242.html> <http://developer.apple.com/samplecode/EmptyFS/index.html> <http://developer.apple.com/samplecode/MFSLives/index.html> Looks like there are no makefiles in the Apple/Darwin world. So what tools should I use instead? <http://www.opendarwin.org/projects/darwinbuild/> S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... At 13:46 +0300 3/12/06, Kirill Kuvaldin wrote: Unfortunately Apple documentation about VFS KEXTs looks strictly limited. :( I need to rev this Q&A to reference my new samples, but I haven't got around to it yet. In the meantime, you can find them here. I strongly recommend that you start with these samples rather than trying to work with one of the production file systems. The samples were written specifically as sample code, whereas the production file systems have accumulated cruft over decades of development. At 13:46 +0300 3/12/06, Kirill Kuvaldin wrote: Well, we do have makefiles (the kernel builds that way, for example), but not all projects use them. "msdosfs" has an old Project Builder project. What you should do about that depends on your circumstances. Options include: o Most Darwin projects will build using DarwinBuild, but I haven't tried this myself with "msdosfs". o If you open the project with Xcode, it will do a reasonable job of converting the project to a more modern format (don't forget to upgrade the targets to the native format). You then only have to worry about the semi-private header files that aren't included in the standard developer tools (-: o Alternatively, just copy the source files over to a modern Xcode project (like the one that ships inside MFSLives) and start from there. o Once you have something building in Xcode, you can build it from the command line using "xcodebuild". o Alternatively, it's easy to look at the Xcode build log to see the magic that you have to do to build a KEXT using a makefile. It really depends on your final goal. If you're looking for something makefile-based because that's what your build systems uses on other platforms, it's worth the effort setting up a makefile. If you're just experimenting, do it in Xcode: you'll get further faster. This email sent to site_archiver@lists.apple.com