Re: Question about dynamic and static libraries
Re: Question about dynamic and static libraries
- Subject: Re: Question about dynamic and static libraries
- From: Eric Albert <email@hidden>
- Date: Tue, 27 Dec 2005 14:10:47 -0800
On Dec 27, 2005, at 1:02 PM, Art Isbell wrote:
On Dec 27, 2005, at 10:14 AM, Brant Sears wrote:
Then, there are two alias (or perhaps a symbolic link? I'm not sure
what the difference is.)
files created that are both .dylibs with different names.
An alias is restricted to HFS file systems (i.e., only Macs) whereas
a symbolic link is a Unix file system concept. A symbolic link points
to the path of the original file so that if the original file is
moved, the symbolic link breaks. An alias points to the HFS file
system handle of the original file (not sure of the correct
terminology because I come from a Unix, not a Mac world) so that when
the file is moved, the alias isn't broken. On the flip side, I
believe that an alias would break if the original file were replaced
by a file with an identical path whereas a symbolic link would not.
So they each have their advantages and disadvantages.
Actually, aliases are supported (for some sense of "supported") on all
file systems Mac OS X supports. On file systems without HFS-style file
IDs, the Alias Manager backs off to paths and in those cases an alias
behaves similarly to a symlink (except that it still isn't
transparently resolved by BSD APIs).
-Eric
_______________________________________________
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