Fujimoto Hisa
hisa****@fobj*****
Sun Jan 21 08:47:30 JST 2007
On 2007/01/21, at 5:07, Laurent Sansonetti wrote: > > On Jan 20, 2007, at 9:02 PM, jeanp****@gmail***** wrote: > >> On 1/20/07, Jacob Wallström <jacob****@ghost*****> >> wrote: >> I tried an upgrade but it wouldn't work without /Library/ >> BridgeSupport installed. It would be great if I could upgrade to 1.0 >> without requiring Leopard for my product. >> >> indeed, it might be nice if there were a build target for the >> framework that was fully embeddable - included the contents of / >> Library/BridgeSupport in the framework itself. Indeed. For each framework, best location for putting metadata may be inside of the framework itself. Because each metadata is just reflection for each framework really and it better a framework has all resource for itself. Why header files are put in the Headers of a framework dir? :) This may be important for a optional 3rd party framework especially. Well, a metadata file which put into there should be searchable by the Bridge Support system, like Jacob said so. For example about the location ... Foundatation.framework/Resoruces/metadata.xml WiiRemote.framework/Resources/metadata.xml Foundatation.framework/Library/BridgeSupport/metadata.xml WiiRemote.framework/Library/BridgeSupport/metadata.xml ... > In fact the plan is to add a BridgeSupport directory inside the > current application bundle / RubyCocoa.framework and use them as > possible locations for metadata files. But I didn't do it... yet (to > be honest, I forgot about it :)). it's better location inside the target framework in addition to there. thanks! -- hisa
