BridgeSupport file is missing

[GoogleCodeExporter]

In Leopard, a new mechanism called BridgeSupport was introduced to provide 
machine-readable 
metadata regarding APIs that cannot be introspected at runtime. This metadata 
is read by 
scripting languages bridges, PyObjC (for Python) and RubyCocoa (for RubyCocoa), 
which are both 
bundled with the system.

http://trac.macosforge.org/projects/bridgesupport

Please consider covering MacFUSE.framework with BridgeSupport, so that people 
can use it from 
Python and Ruby with a good user-experience. For example, some constants are 
missing without 
a bridge support file. Since you are providing packages for both Tiger and 
Leopard, you might 
want to only cover the Leopard package.

You can read more with BridgeSupport(5) and gen_bridge_metadata(1).  I was able 
to produce a 
bridge support file for MacFUSE by typing the following:

$ sudo mkdir /Library/Frameworks/MacFUSE.framework/Resources/BridgeSupport
$ sudo gen_bridge_metadata -f MacFUSE > 
/Library/Frameworks/MacFUSE.framework/Resources/BridgeSupport/MacFUSE.bridgesupp
ort

Original issue reported on code.google.com by laurent....@gmail.com on 10 Jan 2008 at 6:49

[GoogleCodeExporter]

Sounds like a good idea and I agree that it should be done.  I'll play with it 
as
soon as I get a chance or pass it off to someone else who will do it if I don't 
have
time.  Thanks for the very detailed writeup of the issue.

Original comment by inaddr...@gmail.com on 11 Jan 2008 at 7:57

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I've added a post-build script that generates BridgeSupport for 
MacFUSE.framework, so
this should be in the next release (as of revision 772). However, I'm not 
familiar
with BridgeSupport in general. Can you take a quick look at the attached
MacFUSE.bridgesupport file and see if it looks like it is correct?

Original comment by inaddr...@gmail.com on 29 Jan 2008 at 7:20

• Changed state: Fixed

Attachments:

• MacFUSE.bridgesupport

[GoogleCodeExporter]

The attached file seems great. Thanks for the fix :)

Original comment by laurent....@gmail.com on 31 Jan 2008 at 12:50