a676d23a54
In trying to upgrade my mempool instance, I discovered I couldn't build the latest mempool Rust code with my available Rust toolchain. It appears in #4612 the Rust MSRV was bumped without justification, which is reverted here. Note that `Cargo.lock` updates here should ensure the versions of dependent crates use the versions supported by our MSRV. Its possible that the dependency downgrades here break something, but things appear to be running fine for me locally, so figured I'd suggest this upstream. |
||
---|---|---|
.. | ||
src | ||
.gitignore | ||
build.rs | ||
Cargo.lock | ||
Cargo.toml | ||
package.json | ||
README.md | ||
rust-toolchain |
gbt
gbt: rust implementation of the getBlockTemplate algorithm
This project was bootstrapped by napi.
Installing gbt
Installing gbt requires a supported version of Node and Rust.
The build process also requires Rust to be installed.
You can install the project with npm. In the project directory, run:
$ npm install
This fully installs the project, including installing any dependencies and running the build.
Building gbt
If you have already installed the project and only want to run the build, run:
$ npm run build
This command uses the napi build utility to run the Rust build and copy the built library into ./gbt.[TARGET_TRIPLE].node
.
Exploring gbt
After building gbt, you can explore its exports at the Node REPL:
$ npm install
$ node
> require('.').hello()
"hello node"
Available Scripts
In the project directory, you can run:
npm install
Installs the project, including running npm run build-release
.
npm build
Builds the Node addon (gbt.[TARGET_TRIPLE].node
) from source.
Additional cargo build
arguments may be passed to npm build
and npm build-*
commands. For example, to enable a cargo feature:
npm run build -- --feature=beetle
npm build-debug
Alias for npm build
.
npm build-release
Same as npm build
but, builds the module with the release
profile. Release builds will compile slower, but run faster.
npm test
Runs the unit tests by calling cargo test
. You can learn more about adding tests to your Rust code from the Rust book.
Project Layout
The directory structure of this project is:
gbt/
├── Cargo.toml
├── README.md
├── gbt.[TARGET_TRIPLE].node
├── package.json
├── src/
| └── lib.rs
└── target/
Cargo.toml
The Cargo manifest file, which informs the cargo
command.
README.md
This file.
gbt.[TARGET_TRIPLE].node
The Node addon—i.e., a binary Node module—generated by building the project. This is the main module for this package, as dictated by the "main"
key in package.json
.
Under the hood, a Node addon is a dynamically-linked shared object. The "build"
script produces this file by copying it from within the target/
directory, which is where the Rust build produces the shared object.
package.json
The npm manifest file, which informs the npm
command.
src/
The directory tree containing the Rust source code for the project.
src/lib.rs
The Rust library's main module.
target/
Binary artifacts generated by the Rust build.
Learn More
To learn more about Neon, see the Napi-RS documentation.
To learn more about Rust, see the Rust documentation.
To learn more about Node, see the Node documentation.