Do you control the plug-in specification and are the plug-ins a
standard bundle with an Info.plist? If so, why not specify that a GC
plug-in must have a boolean key that indicates that GC is supported.
If the value is false or non-existent, then you can assume it doesn't
support GC.
Aaron
On Aug 8, 2008, at 12:48 AM, André Pang wrote:
Hi all, is there a reasonably easy way to programmatically determine
whether a particular executable on-disk supports garbage
collection? Cocoa methods aren't necessary; all C functions are
welcome. Poking around in an executable's Mach-O headers is fine
too, but I'm not sure what to look for.
My usage scenario is that we're intending to ship an experimental GC
version of our app to some customers, but we have a lot of plugins
for our app, and they won't work under the GC version unless they're
compiled GC-supported. I'd like to display a sheet in the regular,
non-GC version of the app that tells the user which plugins aren't
GC-supported, so I can't simply attempt to preflight the bundle and
see if that fails, since the preflight check would be running on the
non-GC version. Any hints?
