Re: Redefined symbols in linked dylibs
Re: Redefined symbols in linked dylibs
- Subject: Re: Redefined symbols in linked dylibs
- From: "Ben Kennedy" <email@hidden>
- Date: Sun, 26 Oct 2003 01:14:10 -0400
- Organization: Zygoat Creative Technical Services
On 26 10 2003 at 1:01 am -0400, Frank Midgley wrote:
>The only thing I found that worked was not to link against the symlink
>(/usr/lib/libcrypto.dylib) but to link against an actual library
>(/usr/libcrypto.0.9.7.dylib) directly. This unfortunately puts an OS
>dependency on your target but I haven't figured out any other way to
>handle it.
On this advice, I opened up the inspector and attempted to re-specify the
locations for these libs. Before pointing them to the specific libs, I
decided to ensure they were pointing to the generic symlinks first, as a
test. Upon doing so, I realised that Xcode is automatically resolving
the symlink -- so there is actually no choice but to have this dependency now.
In any case, it seems to link properly now without the warnings! I'm not
exactly sure what changed. Oh well.
On a side note -- is there some way to clue Xcode into the fact I want to
re-link? Previously, I would only get those duplicate symbol warnings
once, and not again until it recompiled a source file and relinked.
Maybe this is something to do with the "classic" or whatever (non-
"native") target; I haven't converted it yet.
-ben
--
Ben Kennedy, chief magician
zygoat creative technical services
613-228-3392 | 1-866-466-4628
http://www.zygoat.ca
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.