I forgot to mention, Package Management and Wrangling Third-Party Software Dependencies sections coming later.
I have this skeleton drafted out, but since they’re not done, they are omitted for now:
Package Management
The Manifest File
In order to fetch code from an external location, all dependencies must be listed in the
build manifest file - build.zig.zon. This way, package-related tooling can have a complete list of possible dependencies without the need to execute arbitrary code.
The Package Hash
Depending on a Zig Module
Making a Release
mention zig fetch
Dealing with Symlinks
Running a Tool from a Dependency
nasm example
Wrangling Third-Party Software Dependencies
When a project that you depend on uses the Zig Build System, you can refer to
the Package Management section. However, there is plenty of useful software out there whose maintainers have no plan to migrate to Zig. Fortunately, even such projects can be added seamlessly to the Zig ecosystem with the following techniques. Note that bullying the maintainers into using Zig is not listed here!!