Re: Different versions of framework?
Re: Different versions of framework?
- Subject: Re: Different versions of framework?
- From: Mark Lilback <email@hidden>
- Date: Sat, 4 Dec 2004 09:26:14 -0600
At 1:13 PM -0500 12/3/2004, Bob Ippolito wrote:
It has recently come to my attention that using versioned frameworks
without binary compatible APIs simply doesn't work. This isn't a
problem with the dyld runtime, simply a problem with gcc's compiler
and linker. A big one.
You misunderstand the point of versioning. Take a look at the
Frameworks chapter of the System Overview documentation. The most
relevant part would be "The major versioning scheme provides for
backward compatibility."
The idea is that you ship version 1.0 of your application that depend
on version A of your framework that gets installed in
/Library/Frameworks. When you ship version 2.0, you need to make
major changes to the APIs for the framework. But, when the framework
is updated, you don't want to stop users from running the old version
of your application.
Therefore all new versions of your application link to version B of
the framework, but you include version A so that old versions of your
application will still run.
If you look at the JavaVM framework you'll see versions for 1.2, 1.3,
1.3.1, 1.4.2. Applications compiled under 10.0 for Java 1.2 will
still work, but all new apps are compiled to work with 1.4.2, unless
the developer explicitly links to an older version like you described.
--
__________________________________________________________________________
"The fetters imposed on liberty at home have ever
Mark J. Lilback been forged out of the weapons provided for
<email@hidden> defence against real, pretended, or imaginary
http://www.lilback.com/ dangers from abroad." -- James Madison
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden