do-dyn

Unnamed repository; edit this file 'description' to name the repository.
git clone git://code.mfashby.net:/do-dyn
Log | Files | Refs | README

build.zig.zon (2862B)


      1 .{
      2     .name = "do-dyn",
      3     // This is a [Semantic Version](https://semver.org/).
      4     // In a future version of Zig it will be used for package deduplication.
      5     .version = "0.0.0",
      6 
      7     // This field is optional.
      8     // This is currently advisory only; Zig does not yet do anything
      9     // with this value.
     10     //.minimum_zig_version = "0.11.0",
     11 
     12     // This field is optional.
     13     // Each dependency must either provide a `url` and `hash`, or a `path`.
     14     // `zig build --fetch` can be used to fetch all dependencies of a package, recursively.
     15     // Once all dependencies are fetched, `zig build` no longer requires
     16     // Internet connectivity.
     17     .dependencies = .{
     18         // See `zig fetch --save <url>` for a command-line interface for adding dependencies.
     19         //.example = .{
     20         //    // When updating this field to a new URL, be sure to delete the corresponding
     21         //    // `hash`, otherwise you are communicating that you expect to find the old hash at
     22         //    // the new URL.
     23         //    .url = "https://example.com/foo.tar.gz",
     24         //
     25         //    // This is computed from the file contents of the directory of files that is
     26         //    // obtained after fetching `url` and applying the inclusion rules given by
     27         //    // `paths`.
     28         //    //
     29         //    // This field is the source of truth; packages do not come from an `url`; they
     30         //    // come from a `hash`. `url` is just one of many possible mirrors for how to
     31         //    // obtain a package matching this `hash`.
     32         //    //
     33         //    // Uses the [multihash](https://multiformats.io/multihash/) format.
     34         //    .hash = "...",
     35         //
     36         //    // When this is provided, the package is found in a directory relative to the
     37         //    // build root. In this case the package's hash is irrelevant and therefore not
     38         //    // computed. This field and `url` are mutually exclusive.
     39         //    .path = "foo",
     40         //},
     41     },
     42 
     43     // Specifies the set of files and directories that are included in this package.
     44     // Only files and directories listed here are included in the `hash` that
     45     // is computed for this package.
     46     // Paths are relative to the build root. Use the empty string (`""`) to refer to
     47     // the build root itself.
     48     // A directory listed here means that all files within, recursively, are included.
     49     .paths = .{
     50         // This makes *all* files, recursively, included in this package. It is generally
     51         // better to explicitly list the files and directories instead, to insure that
     52         // fetching from tarballs, file system paths, and version control all result
     53         // in the same contents hash.
     54         "",
     55         // For example...
     56         //"build.zig",
     57         //"build.zig.zon",
     58         //"src",
     59         //"LICENSE",
     60         //"README.md",
     61     },
     62 }