Re: NKE dependencies
Re: NKE dependencies
- Subject: Re: NKE dependencies
- From: Michael Tuexen <email@hidden>
- Date: Thu, 20 Apr 2006 20:40:45 +0200
Hi Dean,
see my comments in-line.
Best regards
Michael
On Apr 20, 2006, at 8:29 PM, Dean Reece wrote:
On Apr 20, 2006, at 11:14, Michael Tuexen wrote:
Dear all,
I have a NKE which has a dependancy to com.apple.kernel.
To get it working on 10.4.6 on PPC I have
<dict>
<key>com.apple.kernel</key>
<string>8.6.0</string>
</dict>
in the corresponding Info.plist file.
I also built the NKE as a universal binary but I figured out that
10.4.6 on Intel uses 8.6.1.
How can I build a universal binary which loads on both? So how can
I wildcard the last number?
Furthmore I think the NKE will load on all Tiger systems? So is it
possible to state something like 8.?.? for the version?
Thank you very much for your help.
Best regards
Michael
You cannot - wildcarding is intentionally not supported.
com.apple.kernel is only for building kexts that run on a single OS
release, and in this case the PPC and Intel releases are distinct
(thus the unique kernel version numbers). We strongly recommend
against using com.apple.kernel for any commercial
Will these numbers likely be the same in the future?
product; it is intended for use during development, or special
environments such as college labs where release-to-release binary
compatibility (RRBC) isn't a requirement.
It is not a commercial product. It is a open source implementation of
a transport protocol (SCTP)
which is basically the same code as used in future FreeBSD stacks,
but it is provided as
a loadable kernel extension.
You really should be using the KPI identifiers
(com.apple.kpi.whatever) or, at least the old-style identifiers
(com.apple.kernel.whatever) if at all possible. If the
functionality you need is not available in one of those symbol
sets, then you should file a feature request asking for that
functionality to be added via supported KPI.
Since I currently see only two implementations of such protocols
(SCTP and DCCP) I doubt that
it makes sense to get an API standardized... It basically uses a lot
of stuff within the kernel,
just like the TCP implementation in the kernel.
This is documented at: <http://developer.apple.com/documentation/
Darwin/Conceptual/KEXTConcept/KEXTConceptDependencies/
kext_dependencies.html>
Thanks.
Hope this helps,
- Dean
_______________________________________________
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