m17e.co
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 = .DOOM_fire_zig,
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.16.0-dev.1364+f0a3df98d",
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 = 0x1db583a44ac8065, // 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.16.0-dev.1364+f0a3df98d",
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 // See `zig fetch --save <url>` for a command-line interface for adding dependencies.
40 //.example = .{
41 // // When updating this field to a new URL, be sure to delete the corresponding
42 // // `hash`, otherwise you are communicating that you expect to find the old hash at
43 // // the new URL.
44 // .url = "https://example.com/foo.tar.gz",
45 //
46 // // This is computed from the file contents of the directory of files that is
47 // // obtained after fetching `url` and applying the inclusion rules given by
48 // // `paths`.
49 // //
50 // // This field is the source of truth; packages do not come from a `url`; they
51 // // come from a `hash`. `url` is just one of many possible mirrors for how to
52 // // obtain a package matching this `hash`.
53 // //
54 // // Uses the [multihash](https://multiformats.io/multihash/) format.
55 // .hash = "...",
56 //
57 // // When this is provided, the package is found in a directory relative to the
58 // // build root. In this case the package's hash is irrelevant and therefore not
59 // // computed. This field and `url` are mutually exclusive.
60 // .path = "foo",
61
62 // // When this is set to `true`, a package is declared to be lazily
63 // // fetched. This makes the dependency only get fetched if it is
64 // // actually used.
65 // .lazy = false,
66 //},
67 },
68
69 // Specifies the set of files and directories that are included in this package.
70 // Only files and directories listed here are included in the `hash` that
71 // is computed for this package. Only files listed here will remain on disk
72 // when using the zig package manager. As a rule of thumb, one should list
73 // files required for compilation plus any license(s).
74 // Paths are relative to the build root. Use the empty string (`""`) to refer to
75 // the build root itself.
76 // A directory listed here means that all files within, recursively, are included.
77 .paths = .{
78 ".zigversion",
79 "build.zig",
80 "build.zig.zon",
81 "src",
82 // For example...
83 "LICENSE.md",
84 "README.md",
85 },
86}