Skip navigation.
 
mlRe: linking to private frameworks
FROM : Glenn Andreas
DATE : Thu Sep 30 18:28:32 2004

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_removed>
<http://www.gandreas.com/> oh my!
Mad, Bad, and Dangerous to Know

Related mailsAuthorDate
mllinking to private frameworks Eric Ocean Sep 30, 06:51
mlRe: linking to private frameworks Karin Kosina Sep 30, 12:37
mlRe: linking to private frameworks Greg Hurrell Sep 30, 13:29
mlRe: linking to private frameworks Eric Ocean Sep 30, 18:13
mlRe: linking to private frameworks Glenn Andreas Sep 30, 18:28
mlRe: linking to private frameworks Eric Ocean Sep 30, 19:07
mlRe: linking to private frameworks Frederick Cheung Sep 30, 20:13
mlRe: linking to private frameworks Ken Ferry Sep 30, 22:08
mlRe: linking to private frameworks [solved] Eric Ocean Oct 1, 00:41