Part 17. Interfacing with C

Zig works unusually well with C because it treats C as a first-class part of systems programming.

10 items

Section	Title
1	Why Zig Works Well with C
2	`@cImport`
3	Calling C Functions
4	Using C Structs
5	Linking C Libraries
6	Building Mixed Zig and C Projects
7	Exporting Zig to C
8	ABI Compatibility
9	Working with Headers
10	Wrapping Existing Libraries

Writes › Book › Zig › Part 17. Interfacing with C ›

Why Zig Works Well with C

Zig works unusually well with C because it treats C as a first-class part of systems programming.

Writes › Book › Zig › Part 17. Interfacing with C ›

`@cImport`

@cImport is Zig’s built-in way to import C declarations from header files.

Writes › Book › Zig › Part 17. Interfacing with C ›

Calling C Functions

Calling a C function from Zig has three parts.

Writes › Book › Zig › Part 17. Interfacing with C ›

Using C Structs

A C struct groups several fields into one value.

Writes › Book › Zig › Part 17. Interfacing with C ›

Linking C Libraries

Importing a C header lets Zig understand a C API. Linking gives the final program the actual compiled code.

Writes › Book › Zig › Part 17. Interfacing with C ›

Building Mixed Zig and C Projects

A mixed Zig and C project contains source files from both languages.

Writes › Book › Zig › Part 17. Interfacing with C ›

Exporting Zig to C

Zig can call C, but C can also call Zig.

Writes › Book › Zig › Part 17. Interfacing with C ›

ABI Compatibility

ABI means Application Binary Interface.

Writes › Book › Zig › Part 17. Interfacing with C ›

Working with Headers

C headers are the bridge between Zig and C.

Writes › Book › Zig › Part 17. Interfacing with C ›

Wrapping Existing Libraries

Wrapping a C library means building a Zig layer around it.