Re: thread_policy( ) and thread_policy_set( ) : where are those functions ?
Re: thread_policy( ) and thread_policy_set( ) : where are those functions ?
- Subject: Re: thread_policy( ) and thread_policy_set( ) : where are those functions ?
- From: Kurt Revis <email@hidden>
- Date: Wed, 28 Aug 2002 06:35:47 -0700
You don't want to do this. Kernel.framework is not a framework that
applications can link against. It's just a convenient place to put
headers that are used for building kernel extensions.
Note that MillionMonkeys doesn't have the checkbox next to
Kernel.framework checked, so it doesn't actually try to link against
that framework. It's just there to make it easy for humans to read the
headers in that framework.
I take that back--it actually seems to be there for a reason (so
latency.h can find the sys/kdebug.h in Kernel.framework, instead of the
one in /usr/include, which is missing some things...).
But this is a really unusual thing to need to do. Why are you using MM
as an example in the first place? It doesn't even build out of the box
(need to comment out the #include <bsd/curses.h> in latency.h), has tons
of warnings, and generally does some very weird things.
What may be tripping you up is the fact that it includes headers from
the Kernel framework:
#import <Kernel/mach/thread_policy.h>
Normal code should just use the ones in /usr/include, like this:
#include <mach/thread_policy.h>
I don't know why MM does it that way--the versions in Kernel.framework
are identical to the ones in /usr/include.
--
Kurt Revis
email@hidden
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.