liveBook · Manning

Application binary interface

Also called ABI

An application binary interface is a specification of binary-level conventions, such as data representation and calling conventions, that govern interaction between compiled software components.

How 3 Manning books explain it

Refactoring to Rust

An ABI is a binary-level calling convention and interface specification governing how separately compiled software components interact.

How it is used
Uses low-level protocols to make WebAssembly modules portable across runtimes, languages, and operating systems.
How deep it goes
Defines ABI as binary interoperability and demonstrates runtime integration, but stops short of detailing calling-convention layouts or binary encoding.
Examples
Demonstrates a Rust search module compiled for wasm32-wasi, executed by WasmEdge, and supplied with command-line arguments.
What you can do after
Operate/configure a Rust WebAssembly module for a compatible runtime and pass arguments through its binary interface.

Read how Refactoring to Rust explains application binary interface →

Embedded Software with Rust

An application binary interface specifies binary-level conventions for calling functions, representing data, and interoperating between compiled software components.

How it is used
Supports embedded target selection and interoperability between Rust and C firmware components.
How deep it goes
Defines ABI responsibilities and explains a simplified Cortex-M calling convention, including floating-point and stack-alignment exceptions.
Examples
Uses a five-argument C function to illustrate register and stack placement, and a linker directive to illustrate data-section alignment.
What you can do after
Evaluate/understand ABI compatibility when choosing an embedded target or sharing calls and memory between Rust and C.

Read how Embedded Software with Rust explains application binary interface →

Systems Programming with Zig

An application binary interface specifies how compiled components interact at the binary level, including calling conventions and data representation.

How it is used
Uses the ABI to explain how compiled components cooperate across foreign-function interfaces.
How deep it goes
Defines ABI responsibilities and works through C-compatible data transfer, without specifying a complete calling convention.
Examples
Uses recipe retrieval with caller-provided buffers and CHIP-8 subroutine calls to illustrate binary interfaces.
What you can do after
Apply it via Zig to expose C-compatible recipe data using extern structs and a caller-provided buffer.

Read how Systems Programming with Zig explains application binary interface →

What to know first

Related concepts

Questions about application binary interface

What is application binary interface?

An application binary interface is a specification of binary-level conventions, such as data representation and calling conventions, that govern interaction between compiled software components.

Which Manning books explain application binary interface?

Refactoring to Rust, Embedded Software with Rust and Systems Programming with Zig.

What should I know before learning application binary interface?

Manning books that teach application binary interface usually introduce assembly language and C++ first.

What kinds of application binary interface are there?

Kinds of application binary interface include C ABI compatibility.

What are the parts of application binary interface?

Application binary interface includes calling convention, procedure call standard and memory layout.

What is application binary interface also called?

Application binary interface is also called ABI.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.