Debugging a MIDI Driver (CFPlugin issue)..
Debugging a MIDI Driver (CFPlugin issue)..
- Subject: Debugging a MIDI Driver (CFPlugin issue)..
- From: Jay Vaughan <email@hidden>
- Date: Tue, 4 Apr 2006 14:47:32 +0200
hi all,
I have a MIDI Driver which, prior to my upgrade to XCode 2.2.1 was
building, loading and running just fine on my PPC-based development
system .. but since this upgrade of XCode, the .plugin bundle being
produced fails to load in MIDIServer .. I'm not trying to do anything
special, just produce a new .plugin bundle for debugging.
I've not made any code changes - only upgraded my XCode - so i'm
trying to track down what could be causing the problem with the
.plugin being loaded, and the question i have is, what can be done to
debug this? Is there a way of telling MIDIServer to report any
problems/errors it encounters with loading the .plugin bundle, in a
fashion similar to the way 'kextload' can be told to validate .kexts'
from the command line ..
What happens is, absolutely nothing. The new .plugin bundle is in
the right place, i plug in the device, I'm watching
console.log/debug.log, but its as if the .plugin just doesn't exist
.. it fails to load.
I've tried this so far:
- new UUID (no result)
- verified the class factory function is tied to the new UUID
- gcc 3.1/3.3/4.0 ..
- diff of old, working .plugin bundle with newly-built .plugin (the
binary MIDIDriver is different)
- hand-checked Info.plist for correct uuid/factory member association
- tried re-compiling against the different CoreAudio SDK's - 3.9, 4.0
Are there some kind of tools for debugging CFPlugins' on OSX? Some
kind of .plugin cache under control of the MIDIServer that can be
cleared? Possible that I've run into some XCode 2.2.1 brick-wall?
--
;
Jay Vaughan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden