Re: Linking to libcrypto
Re: Linking to libcrypto
- Subject: Re: Linking to libcrypto
- From: Scott Tooker <email@hidden>
- Date: Mon, 3 Nov 2003 14:39:59 -0800
The part of this "resolving symlinks" bug that Xcode could do better,
is to only resolve the symlink once you need the file for something
(building, for example). Also, if you provide a path to a reference
that uses symlinks, we should keep that path around and not replace it
with the expanded version.
We are working towards solving this in a future release.
Scott
On Nov 3, 2003, at 9:22 AM, Ben Kennedy wrote:
>> I'm not clear what you want to happen then. The symbolic link is just
>> a file name. It lets you (in this case) give a less-specific name and
>> end up with what the system thinks is the best version for you. If
>> you
>> give more-specific names, you (I) would expect to be potentially more
>> version-dependent.
>
> You're right, I think I was being overly naiive, thinking to myself
> "well
> if I point it to libcrypto.dylib [sans explicit version]", then it
> ought
> to work systems that have [any version of] libcrypto". In reality, I
> guess I need to make sure I know what minimum version will be available
> on the deployment systems (10.2 in my case), make sure that same are
> available on my build system, and link against them expressly.
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
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.