Am 25.08.2016 um 12:35 nachm. schrieb Alastair Houghton <alastair@alastairs-place.net>:
What I’d try to do is to isolate all of the kernel or userland specific bits of code somehow, such that your code doesn’t actually need lots of #ifdef UNIT_TEST blocks everywhere. I think a good way to go about this would be to put the code you think you want to test into a static library, with separate targets for your unit tests and the KEXT itself, both of which link to the static library. Then put any userland/kernel-specific stuff in source files specific to those other targets.
Interesting — Good to know, then. I’ll focus my time on that approach. Thanks, - Andrew Keller _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app... This email sent to site_archiver@lists.apple.com