Gabe Venberg
560db87929
Has runner and tester for each day, as well as a runner and tester for all the days. Also has check step for zls.
46 lines
2.2 KiB
Zig
46 lines
2.2 KiB
Zig
.{
|
|
// This is the default name used by packages depending on this one. For
|
|
// example, when a user runs `zig fetch --save <url>`, this field is used
|
|
// as the key in the `dependencies` table. Although the user can choose a
|
|
// different name, most users will stick with this provided value.
|
|
//
|
|
// It is redundant to include "zig" in this name because it is already
|
|
// within the Zig package namespace.
|
|
.name = .aoc2024,
|
|
|
|
// This is a [Semantic Version](https://semver.org/).
|
|
// In a future version of Zig it will be used for package deduplication.
|
|
.version = "0.0.1",
|
|
|
|
// Together with name, this represents a globally unique package
|
|
// identifier. This field is generated by the Zig toolchain when the
|
|
// package is first created, and then *never changes*. This allows
|
|
// unambiguous detection of one package being an updated version of
|
|
// another.
|
|
//
|
|
// When forking a Zig project, this id should be regenerated (delete the
|
|
// field and run `zig build`) if the upstream project is still maintained.
|
|
// Otherwise, the fork is *hostile*, attempting to take control over the
|
|
// original project's identity. Thus it is recommended to leave the comment
|
|
// on the following line intact, so that it shows up in code reviews that
|
|
// modify the field.
|
|
.fingerprint = 0x25105d4386327470, // Changing this has security and trust implications.
|
|
|
|
// Tracks the earliest Zig version that the package considers to be a
|
|
// supported use case.
|
|
.minimum_zig_version = "0.14.0",
|
|
|
|
// Specifies the set of files and directories that are included in this package.
|
|
// Only files and directories listed here are included in the `hash` that
|
|
// is computed for this package. Only files listed here will remain on disk
|
|
// when using the zig package manager. As a rule of thumb, one should list
|
|
// files required for compilation plus any license(s).
|
|
// Paths are relative to the build root. Use the empty string (`""`) to refer to
|
|
// the build root itself.
|
|
// A directory listed here means that all files within, recursively, are included.
|
|
.paths = .{
|
|
"build.zig",
|
|
"build.zig.zon",
|
|
"src",
|
|
},
|
|
}
|