Re: Shared Framework FRAMEWORK_SEARCH_PATHS issue
Re: Shared Framework FRAMEWORK_SEARCH_PATHS issue
- Subject: Re: Shared Framework FRAMEWORK_SEARCH_PATHS issue
- From: Scott Tooker <email@hidden>
- Date: Mon, 13 Mar 2006 15:56:06 -0800
On Mar 13, 2006, at 12:49 PM, Byron Wright wrote:
I am having a problem including a custom framework
(HessianObjC.framework) I created and installed in /Library/
Frameworks/ in another project. I built the framework on XCode 2.2
as a universal binary. When I create a new project and add this
framework I get link errors:
Checking Dependencies
Building ZeroLink launcher /Users/byronwright/Projects/hessianobjc/
trunk/examples/SimpleAppTest/build/SimpleAppTest.build/Debug/
SimpleAppTest.build/Objects-normal/ppc/SimpleAppTest
cd /Users/byronwright/Projects/hessianobjc/trunk/examples/
SimpleAppTest
/usr/bin/gcc-4.0 -o /Users/byronwright/Projects/hessianobjc/
trunk/examples/SimpleAppTest/build/SimpleAppTest.build/Debug/
SimpleAppTest.build/Objects-normal/ppc/SimpleAppTest -arch ppc /
System/Library/PrivateFrameworks/ZeroLink.framework/Resources/
libZeroLinkAppStub.a -Wl,-all_load -L/Users/byronwright/Projects/
hessianobjc/trunk/examples/SimpleAppTest/build/Debug -F/Users/
byronwright/Projects/hessianobjc/trunk/examples/SimpleAppTest/build/
Debug -framework Cocoa -framework HessianObjC -framework ZeroLink -F/
System/Library/PrivateFrameworks/ -isysroot /Developer/SDKs/
MacOSX10.4u.sdk -Wl,-x -Wl,-unexported_symbols_list -Wl,/System/
Library/PrivateFrameworks/ZeroLink.framework/Versions/A/Resources/
ZeroLinkAppStub.nexp -Wl,-sectcreate -Wl,__TEXT -Wl,__zerolink -Wl,/
Users/byronwright/Projects/hessianobjc/trunk/examples/SimpleAppTest/
build/SimpleAppTest.build/Debug/SimpleAppTest.build/Objects-normal/
ppc/SimpleAppTest.zerolink
/usr/bin/ld: can't locate framework for: -framework HessianObjC
collect2: ld returned 1 exit status
Do I have to explicitly specify the framework search path
[FRAMEWORK_SEARCH_PATHS, -F] ? Is XCode only searching "/Developer/
SDKs/MacOSX10.4u" root path for the frameworks? As you can see I am
building the test application as a universal binary also.
You'll need to add "/Library/Frameworks/" to the framework search path
build setting. Don't worry about the "/Developer/SDKS/MacOSX10.4u"
root path. Xcode is adding that automatically when an SDK is being used.
Another option is to build the HessianObjC framework into the same
build products location as the above project. Then Xcode will pick up
the currently built version of the framework when building the new
project (this also allows you to keep development versions of the
framework local to your work and not impact your system).
Scott
Thanks,
Byron
_______________________________________________
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
_______________________________________________
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