Re: Problems with InterfaceBuilder.framework in xcode 2.5
Re: Problems with InterfaceBuilder.framework in xcode 2.5
- Subject: Re: Problems with InterfaceBuilder.framework in xcode 2.5
- From: "Mike Marino" <email@hidden>
- Date: Wed, 7 Nov 2007 11:40:27 -0800
Hi Rick, thanks for the quick response. That indeed solved the
problem, I was unaware that xcode 2.5's ld would not handle
@loader_path correctly. Just to note I did receive additional linking
errors, though no undefined symbols, so others who use this may have
to pass additional -dylib_file flags if they use symbols in the missed
libraries. The errors I received:
/Developer/usr/bin/../libexec/gcc/powerpc-apple-darwin8/4.0.1/ld:
warning can't open dynamic library:
@loader_path/../../../DevToolsSupport.framework/Versions/A/DevToolsSupport
referenced from:
/Developer/Library/PrivateFrameworks/DevToolsRemoteClient.framework/Versions/A/DevToolsRemoteClient
(checking for undefined symbols may be affected) (No such file or
directory, errno = 2)
/Developer/usr/bin/../libexec/gcc/powerpc-apple-darwin8/4.0.1/ld:
warning can't open dynamic library:
@loader_path/../../../DevToolsCore.framework/Versions/A/DevToolsCore
referenced from:
/Developer/Library/PrivateFrameworks/DevToolsRemoteClient.framework/Versions/A/DevToolsRemoteClient
(checking for undefined symbols may be affected) (No such file or
directory, errno = 2)
which can be fixed the same way as Rick noted, i.e.:
- Add the following to the Other Linker Flags build setting:
-dylib_file
@loader_path/../../../DevToolsCore.framework/Versions/A/DevToolsCore:$
(DEVELOPER_LIBRARY_DIR)/PrivateFrameworks/DevToolsCore.framework/Versions/A/DevToolsCore
-dylib_file
@loader_path/../../../DevToolsSupport.framework/Versions/A/DevToolsSupport:$
(DEVELOPER_LIBRARY_DIR)/PrivateFrameworks/DevToolsSupport.framework/Versions/A/DevToolsSupport
Cheers, Mike
On Nov 7, 2007 11:08 AM, Rick Ballard <email@hidden> wrote:
> On Nov 6, 2007, at 8:36 PM, Mike Marino wrote:
>
> > I have recently upgraded to xcode 2.5 and am linking a project against
> > the InterfaceBuilder.framework. In xcode2.5, this framework has been
> > moved from /System/Library/Frameworks to <xcode 2.5
> > dir>/Library/Frameworks. I am seeing the following error:
> >
> > /Developer/usr/bin/../libexec/gcc/powerpc-apple-darwin8/4.0.1/ld:
> > warning can't open dynamic library:
> > @loader_path/../../../../PrivateFrameworks/
> > DevToolsRemoteClient.framework/Versions/A/DevToolsRemoteClient
> > referenced from:
> > /Developer/Library/Frameworks/InterfaceBuilder.framework/
> > InterfaceBuilder
> > (checking for undefined symbols may be affected) (No such file or
> > directory, errno = 2)
>
> Xcode 2.5's ld cannot parse the @loader_path-relative load paths in a
> framework when you link against it. I expect that the steps for
> dealing with IB 2.5's InterfaceBuilder.framework will be technoted,
> but since no technote is available yet, here's the summary:
>
> - For every target that links against InterfaceBuilder.framework:
>
> - Open the Get Info window for the target in Xcode and select the
> Build pane.
>
> - Add the following to the Framework Search Paths build setting:
> "$(DEVELOPER_FRAMEWORKS_DIR)"
>
> - Add the following to the Other Linker Flags build setting:
> -dylib_file @loader_path/../../../../PrivateFrameworks/
> DevToolsRemoteClient.framework/Versions/A/DevToolsRemoteClient:$
> (DEVELOPER_LIBRARY_DIR)/PrivateFrameworks/
> DevToolsRemoteClient.framework/Versions/A/DevToolsRemoteClient
> -dylib_file @loader_path/../../../../PrivateFrameworks/
> DevToolsFoundation.framework/Versions/A/DevToolsFoundation:$
> (DEVELOPER_LIBRARY_DIR)/PrivateFrameworks/DevToolsFoundation.framework/
> Versions/A/DevToolsFoundation
>
> - Add a shell script build phase to the target that does the following:
> install_name_tool -change "${DEVELOPER_LIBRARY_DIR}/Frameworks/
> InterfaceBuilder.framework/Versions/A/InterfaceBuilder" /System/
> Library/Frameworks/InterfaceBuilder.framework/Versions/A/
> InterfaceBuilder "${TARGET_BUILD_DIR}/${EXECUTABLE_PATH}"
>
> InterfaceBuilder from both Xcode 2.5 and earlier releases of Xcode
> should be able to load the resulting plugin or framework.
>
> - Rick
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden