Re: Dynamic Library being not very dynamic?
Re: Dynamic Library being not very dynamic?
- Subject: Re: Dynamic Library being not very dynamic?
- From: Stephane Sudre <email@hidden>
- Date: Mon, 13 Dec 2004 18:46:17 +0100
On 13 déc. 04, at 18:31, Chris Espinosa wrote:
On Dec 13, 2004, at 2:47 AM, stephane sudre wrote:
I'm using libcrypto in a project.
To use it, I added -lcrypto. The project is built on Mac OS X 10.3.
The issue I'm seeing is that it looks like the dynamic behavior is
lost.
When I run the project on 10.3, no problem. When it's run on Mac OS X
10.2.8, it crashes because it's trying to load against
libcrypto.0.9.7 which is not available on Mac OS X 10.2.8.
What's the appropriate way to link against a dynamic library so that
it stays dynamic?
If you want to build an executable that runs on earlier versions of
the Mac OS, you have to build it against the SDK for that OS.
Libraries are forward-compatible but not necessarily
backwards-compatible.
Select your project icon in Xcode and do Get Info. On the General pane
select the 10.2 SDK, clean, and rebuild.
http://developer.apple.com/documentation/DeveloperTools/Conceptual/
cross_development/Concepts/cd_overview.html
Ok, so it looks like that I will need to compile this on a 10.1 machine
because I need to be 10.1.1 compatible. (as I'm not using Xcode but
Project Builder on 10.3).
I find it a bit strange that to have the link being correctly done, you
have to use one of the Mac OS SDK. Because it would mean that if you
want to use specific features in 10.3 and you have to be 10.2
compatible, you can't have access to the new API.
Strange...
_______________________________________________
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