In article <[EMAIL PROTECTED]>, "Christiaan Hofman" <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 12, 2008 at 3:47 PM, Adam Maxwell <[EMAIL PROTECTED]> wrote: > > > In article <[EMAIL PROTECTED]>, > > Christiaan Hofman <[EMAIL PROTECTED]> wrote: > > > > > I'm a bit confused about the Leopard bundle in the FileView framework. > > > It links to tyhe FileView framework, at @executable_path/../Frameworks/ > > > FileView.framework/Versions/A/FileView. However from the bundle > > > executable that path does not exist. So isn't that a problem? Does it > > > work because the FileView mach-O is guaranteed to be already loaded? > > > > I'm not sure if dyld needs that path since the framework loads the > > bundle; you should be able to link it with -undefined_suppress and it > > will still work. I was originally linking it via the bundle_loader > > flag, but building is cleaner with a separate target that does > > Framework, Bundle, Copy in proper order. Why would > > @executable_path/../Frameworks... not be a valid path, though? > > > > > Because the bundle is located somehwre completely different, so > @executable_path/../Frameworks does not exist. When the bundle is loaded, @executable_path is /path/to/BibDesk.app/Contents/MacOS/BibDesk, and relative to that ../Frameworks should exist. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
