build.zig.zon (2049B)
1 .{ 2 // This is the default name used by packages depending on this one. For 3 // example, when a user runs `zig fetch --save <url>`, this field is used 4 // as the key in the `dependencies` table. Although the user can choose a 5 // different name, most users will stick with this provided value. 6 // 7 // It is redundant to include "zig" in this name because it is already 8 // within the Zig package namespace. 9 .name = .yaml, 10 11 // This is a [Semantic Version](https://semver.org/). 12 // In a future version of Zig it will be used for package deduplication. 13 .version = "0.0.0", 14 15 // Together with name, this represents a globally unique package 16 // identifier. This field is generated by the Zig toolchain when the 17 // package is first created, and then *never changes*. This allows 18 // unambiguous detection of one package being an updated version of 19 // another. 20 // 21 // When forking a Zig project, this id should be regenerated (delete the 22 // field and run `zig build`) if the upstream project is still maintained. 23 // Otherwise, the fork is *hostile*, attempting to take control over the 24 // original project's identity. Thus it is recommended to leave the comment 25 // on the following line intact, so that it shows up in code reviews that 26 // modify the field. 27 .fingerprint = 0xea31a9840416933b, // Changing this has security and trust implications. 28 29 // Tracks the earliest Zig version that the package considers to be a 30 // supported use case. 31 .minimum_zig_version = "0.15.2", 32 33 // This field is optional. 34 // Each dependency must either provide a `url` and `hash`, or a `path`. 35 // `zig build --fetch` can be used to fetch all dependencies of a package, recursively. 36 // Once all dependencies are fetched, `zig build` no longer requires 37 // internet connectivity. 38 .dependencies = .{}, 39 .paths = .{ 40 "build.zig", 41 "build.zig.zon", 42 "src", 43 // For example... 44 //"LICENSE", 45 //"README.md", 46 }, 47 }