site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Thanks. H Best Regards, {Plum} /o\ // \\ The ASCII \\ // Ribbon Campaign \V/ Against HTML /A\ eMail! // \\ _______________________________________________ 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... I have been using vim and Makefiles as the main build tools in my work and study for more than ten years. On the Mac I have no problem whatsoever using Xcode for managing projects. Quite often I still use vim for editing the source files. I certainly don't buy the argument that GUIs are inherrently less efficient... 90% of it is what you're used to. Just like in the vi vs emacs debate. (Also something like: osascript -e 'tell application "Xcode" to add file "file" to project "proj"' would probably work too if you dislike the mouse that much.) So there is absolutely no way to skip using Xcode??? I cannot believe that!! Like I said in my first post, I'm sure you can write a Makefile to do what Xcode does to build a kext. But it is not trivial, e.g. you have to generate an info structure and link it in under a certain symbol. You're welcome to examine the Xcode build output to see what you need to do to avoid using it. in fact it depends , what you do , if you have a big project Xcode becomes a problem an other thing , if u maintain a cross-arch-os driver src, it's better to use a makefile layer This email sent to site_archiver@lists.apple.com