Application binary interface

An application binary interface (ABI) is an <a href="/facts/Interface_(computing)/zdfp8unT">interface</a> exposed by <a href="/facts/Software/RP79lVSW">software</a> that is defined for in-<a href="/facts/Process_(computing)/Vcq7EnUV">process</a> <a href="/facts/Machine_code/bgdQ1Fxf">machine code</a> access. Often, the exposing software is a <a href="/facts/Library_(computing)/xRzL3P7q">library</a>, and the consumer is a <a href="/facts/Computer_program/e38jH9N9">program</a>.
An ABI is at a relatively low-level of <a href="/facts/Abstraction_(computer_science)/hAnxmJle">abstraction</a>. Interface compatibility depends on the target <a href="/facts/Computer_hardware/8jSjsCNv">hardware</a> and the <a href="/facts/Software_build/uTz1koQy">software build</a> <a href="/facts/Toolchain/SmlWCJhY">toolchain</a>. In contrast, an <a href="/facts/Application_programming_interface/GMlN4vUr">application programming interface</a> (API) defines access in <a href="/facts/Source_code/o9J6Jv23">source code</a> which is a relatively high-level, hardware-independent, and <a href="/facts/Human-readable/GDE1fpHT">human-readable</a> format. An API defines interface at the source code level, before compilation, whereas an ABI defines an interface to compiled code.
API compatibility is generally the concern for <a href="/facts/System_design/hFWYoaNP">system design</a> and of the toolchain. However, a <a href="/facts/Programmer/WGTS1Jv9">programmer</a> may have to deal with an ABI directly when writing a program in multiple <a href="/facts/Programming_language/cWTYbgWa">languages</a> or <a href="/facts/Compiler/WNfCDFJe">compilers</a>.
A complete ABI enables a program that supports an ABI to run without modification on multiple operating systems that provide the ABI. The target system must provide any required libraries (that implement the ABI), and there may be other prerequisites.

Application binary interface open-in-new

Application binary interface