Re: Problem with linking against a private framework
Re: Problem with linking against a private framework
- Subject: Re: Problem with linking against a private framework
- From: Julio Cesar Silva dos Santos <email@hidden>
- Date: Tue, 3 Jan 2006 16:48:45 -0200
Yes, you should change the installation path of your framework. Open
your framework project in XCode, control-click on Target's icon and
select 'Get Info'. Select the 'Build' tab and change the value for
Installation Directory from ($HOME)/Applications to
@executable_path/../Frameworks and build it again.
Julio Cesar Santos
email@hidden
eMac 1GHz ComboDrive
640MB RAM
Linux User #359973
On 03/01/2006, at 16:17, Damien Sorresso wrote:
I've got a loadable bundle that relies on a private framework I'm
embedding. The framework is copied into the bundle's "Frameworks"
directory, and I'm linking against it in Xcode, but whenever the
bundle is loaded, the app complains that it couldn't find the
framework in /Library/Frameworks.
This is getting really frustrating. I've checked everything in
Apple's framework guide, and I'm pretty sure I'm doing everything
correctly. Do I need to add anything to my frameworks search paths
for deployment?
--
Damien Sorresso
Macintosh Developer
Computer Infrastructure Support Services
Illinois State University
email@hidden
309.438.5777
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden