-
Notifications
You must be signed in to change notification settings - Fork 1
feat(build): use blst packaged for zig using zig build system
#51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
bd52509
feat(build): use `blst` packaged for zig using zig build system
spiral-ladder 1ad6b3e
update naming for lib for upload-artifact step
spiral-ladder c08b69e
update name: blst.zig -> blst
spiral-ladder 32ece46
update package.json
spiral-ladder File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,91 +1,21 @@ | ||
| .{ | ||
| // 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 = .blst_z, | ||
|
|
||
| // This is a [Semantic Version](https://semver.org/). | ||
| // In a future version of Zig it will be used for package deduplication. | ||
| .version = "0.0.0", | ||
|
|
||
| // 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 = 0xfbd83f934c5ddb5, // 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", | ||
|
|
||
| // This field is optional. | ||
| // Each dependency must either provide a `url` and `hash`, or a `path`. | ||
| // `zig build --fetch` can be used to fetch all dependencies of a package, recursively. | ||
| // Once all dependencies are fetched, `zig build` no longer requires | ||
| // internet connectivity. | ||
| .dependencies = .{ | ||
| // See `zig fetch --save <url>` for a command-line interface for adding dependencies. | ||
| //.example = .{ | ||
| // // When updating this field to a new URL, be sure to delete the corresponding | ||
| // // `hash`, otherwise you are communicating that you expect to find the old hash at | ||
| // // the new URL. If the contents of a URL change this will result in a hash mismatch | ||
| // // which will prevent zig from using it. | ||
| // .url = "https://example.com/foo.tar.gz", | ||
| // | ||
| // // This is computed from the file contents of the directory of files that is | ||
| // // obtained after fetching `url` and applying the inclusion rules given by | ||
| // // `paths`. | ||
| // // | ||
| // // This field is the source of truth; packages do not come from a `url`; they | ||
| // // come from a `hash`. `url` is just one of many possible mirrors for how to | ||
| // // obtain a package matching this `hash`. | ||
| // // | ||
| // // Uses the [multihash](https://multiformats.io/multihash/) format. | ||
| // .hash = "...", | ||
| // | ||
| // // When this is provided, the package is found in a directory relative to the | ||
| // // build root. In this case the package's hash is irrelevant and therefore not | ||
| // // computed. This field and `url` are mutually exclusive. | ||
| // .path = "foo", | ||
| // | ||
| // // When this is set to `true`, a package is declared to be lazily | ||
| // // fetched. This makes the dependency only get fetched if it is | ||
| // // actually used. | ||
| // .lazy = false, | ||
| //}, | ||
| // zig fetch https://github.com/supranational/blst/archive/refs/tags/v0.3.13.tar.gz | ||
| .blst = .{ | ||
| .url = "https://github.com/supranational/blst/archive/refs/tags/v0.3.13.tar.gz", | ||
| .hash = "N-V-__8AAHB4OgByNs3JJNXs9f2gxmbJBYqM7HBRHfmwZa-e", | ||
| .url = "git+https://github.com/ChainSafe/blst.git#4d5bbcc0dd06f80b76fb124420c899570a4dd1e4", | ||
| .hash = "blst_zig-0.0.0-cnAxzogIAAB8nH6TSAGbUtZ6scv2F64aVlcuJabg5HWi", | ||
| }, | ||
| }, | ||
|
|
||
| // 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", | ||
| // For example... | ||
| //"LICENSE", | ||
| //"README.md", | ||
| }, | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had to update this name to match the output in
build.zig.