Re: Unit testing kexts
Re: Unit testing kexts
- Subject: Re: Unit testing kexts
- From: Andrew Keller <email@hidden>
- Date: Thu, 25 Aug 2016 17:20:56 -0400
Am 25.08.2016 um 12:35 nachm. schrieb Alastair Houghton <email@hidden>:
>
> 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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden