mirror of
https://github.com/moparisthebest/curl
synced 2025-02-28 17:31:46 -05:00
ABI: remove the ascii logo
and made the indent level to 1
This commit is contained in:
parent
fc69e2f7ec
commit
5b9a006b8f
@ -1,63 +1,55 @@
|
|||||||
_ _ ____ _
|
|
||||||
___| | | | _ \| |
|
|
||||||
/ __| | | | |_) | |
|
|
||||||
| (__| |_| | _ <| |___
|
|
||||||
\___|\___/|_| \_\_____|
|
|
||||||
|
|
||||||
libcurl's binary interface
|
|
||||||
|
|
||||||
ABI - Application Binary Interface
|
ABI - Application Binary Interface
|
||||||
----------------------------------
|
==================================
|
||||||
|
|
||||||
"ABI" describes the low-level interface between an application program and a
|
"ABI" describes the low-level interface between an application program and a
|
||||||
library. Calling conventions, function arguments, return values, struct
|
library. Calling conventions, function arguments, return values, struct
|
||||||
sizes/defines and more.
|
sizes/defines and more.
|
||||||
|
|
||||||
[Wikipedia has a longer description](http://en.wikipedia.org/wiki/Application_binary_interface)
|
[Wikipedia has a longer description](http://en.wikipedia.org/wiki/Application_binary_interface)
|
||||||
|
|
||||||
Upgrades
|
Upgrades
|
||||||
--------
|
--------
|
||||||
|
|
||||||
In the vast majority of all cases, a typical libcurl upgrade does not break
|
In the vast majority of all cases, a typical libcurl upgrade does not break
|
||||||
the ABI at all. Your application can remain using libcurl just as before,
|
the ABI at all. Your application can remain using libcurl just as before,
|
||||||
only with less bugs and possibly with added new features. You need to read
|
only with less bugs and possibly with added new features. You need to read
|
||||||
the release notes, and if they mention an ABI break/soname bump, you may
|
the release notes, and if they mention an ABI break/soname bump, you may have
|
||||||
have to verify that your application still builds fine and uses libcurl as
|
to verify that your application still builds fine and uses libcurl as it now
|
||||||
it now is defined to work.
|
is defined to work.
|
||||||
|
|
||||||
Version Numbers
|
Version Numbers
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
In libcurl land, you really can't tell by the libcurl version number if that
|
In libcurl land, you really can't tell by the libcurl version number if that
|
||||||
libcurl is binary compatible or not with another libcurl version.
|
libcurl is binary compatible or not with another libcurl version.
|
||||||
|
|
||||||
Soname Bumps
|
Soname Bumps
|
||||||
------------
|
------------
|
||||||
|
|
||||||
Whenever there are changes done to the library that will cause an ABI
|
Whenever there are changes done to the library that will cause an ABI
|
||||||
breakage, that may require your application to get attention or possibly be
|
breakage, that may require your application to get attention or possibly be
|
||||||
changed to adhere to new things, we will bump the soname. Then the library
|
changed to adhere to new things, we will bump the soname. Then the library
|
||||||
will get a different output name and thus can in fact be installed in
|
will get a different output name and thus can in fact be installed in
|
||||||
parallel with an older installed lib (on most systems). Thus, old
|
parallel with an older installed lib (on most systems). Thus, old
|
||||||
applications built against the previous ABI version will remain working and
|
applications built against the previous ABI version will remain working and
|
||||||
using the older lib, while newer applications build and use the newer one.
|
using the older lib, while newer applications build and use the newer one.
|
||||||
|
|
||||||
During the first seven years of libcurl releases, there have only been four
|
During the first seven years of libcurl releases, there have only been four
|
||||||
ABI breakages.
|
ABI breakages.
|
||||||
|
|
||||||
We are determined to bump the SONAME as rarely as possible. Ideally, we
|
We are determined to bump the SONAME as rarely as possible. Ideally, we
|
||||||
never do it again.
|
never do it again.
|
||||||
|
|
||||||
Downgrades
|
Downgrades
|
||||||
----------
|
----------
|
||||||
|
|
||||||
Going to an older libcurl version from one you're currently using can be a
|
Going to an older libcurl version from one you're currently using can be a
|
||||||
tricky thing. Mostly we add features and options to newer libcurls as that
|
tricky thing. Mostly we add features and options to newer libcurls as that
|
||||||
won't break ABI or hamper existing applications. This has the implication
|
won't break ABI or hamper existing applications. This has the implication
|
||||||
that going backwards may get you in a situation where you pick a libcurl
|
that going backwards may get you in a situation where you pick a libcurl that
|
||||||
that doesn't support the options your application needs. Or possibly you
|
doesn't support the options your application needs. Or possibly you even
|
||||||
even downgrade so far so you cross an ABI break border and thus a different
|
downgrade so far so you cross an ABI break border and thus a different
|
||||||
soname, and then your application may need to adapt to the modified ABI.
|
soname, and then your application may need to adapt to the modified ABI.
|
||||||
|
|
||||||
History
|
History
|
||||||
-------
|
-------
|
||||||
|
Loading…
x
Reference in New Issue
Block a user