Re: linking to private frameworks
Re: linking to private frameworks
- Subject: Re: linking to private frameworks
- From: Glenn Andreas <email@hidden>
- Date: Thu, 30 Sep 2004 11:28:32 -0500
Title: Re: linking to private
frameworks
At 9:13 AM -0700 9/30/04, Eric Ocean wrote:
I own the application; I didn't write
it.
Here's the Ld command, and the error
message. According to RuntimeBrowser, the class does in fact exist in
ProKit.
Regards,
Eric Ocean
Ld
/Users/test/Build/MySIMBL.bundle/Contents/MacOS/MySIMBL
cd /Users/test/Desktop/source
/usr/bin/gcc-3.3 -o
/Users/test/Build/MySIMBL.bundle/Contents/MacOS/MySIMBL
-L/Users/test/Build -F/Users/test/Build
-F/System/Library/PrivateFrameworks -filelist
/Users/test/Build/MySIMBL.build/MySIMBL.build/Objects-normal/MySIMBL.LinkFileList -framework Cocoa -framework ProKit -arch ppc
-bundle
ld: Undefined
symbols:
.objc_class_name_NSProAlert
Looking through the symbol information,
.objc_class_name_NSProAlert is a private symbol which means you can't
reference it from an external file.
Granted, I have no idea how a class name can be a private symbol
(looking at other frameworks, all the classes's names are public
symbols), but that's what's happening.
--
Glenn
Andreas
email@hidden
<http://www.gandreas.com/> oh
my!
Mad, Bad, and Dangerous to
Know
_______________________________________________
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