• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Linking to libcrypto
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linking to libcrypto


  • Subject: Re: Linking to libcrypto
  • From: "Ben Kennedy" <email@hidden>
  • Date: Mon, 3 Nov 2003 12:22:40 -0500
  • Organization: Zygoat Creative Technical Services

On 02 11 2003 at 12:31 am -0500, Justin C. Walker 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.

>I suppose that it's the library itself, not the name by which you
>reference it, that dictates this.  If so, I'm not sure my simple
>description is accurate.  For frameworks, I think this works, but for
>plane old shared libraries, Mac OS X may not actually be able to handle
>a different approach to versioning.

Yes, you're probably right, and of course that makes sense.  Half of my
confusion stems from the bizarre filenaming evident on Panther, like you
previously illuminated.

>This may not relate, but don't you have a problem building on 10.3 and
>deploying on 10.2 in general?  Did you install the 10.2 libraries with
>Xcode?  If not, it's possible that you can solve your problem that way.

Using the 10.2 SDK, and making sure I link libcrypto.0.9, it seems to be
working fine for deployment on 10.2 and 10.3 now.

-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.

  • Follow-Ups:
    • Re: Linking to libcrypto
      • From: "Justin C. Walker" <email@hidden>
    • Re: Linking to libcrypto
      • From: Scott Tooker <email@hidden>
References: 
 >Re: Linking to libcrypto (From: "Justin C. Walker" <email@hidden>)

  • Prev by Date: Re: getting Saturn to walk
  • Next by Date: Re: CVS (SCM) commits
  • Previous by thread: Re: Linking to libcrypto
  • Next by thread: Re: Linking to libcrypto
  • Index(es):
    • Date
    • Thread