mirror of
https://github.com/denoland/rusty_v8.git
synced 2024-11-21 20:28:58 +00:00
Stabilize: Release version 129.0.0 of Rusty V8 (#1633)
This commit is contained in:
parent
dd84fa398e
commit
ab019251a4
2
Cargo.lock
generated
2
Cargo.lock
generated
@ -1452,7 +1452,7 @@ checksum = "e51733f11c9c4f72aa0c160008246859e340b00807569a0da0e7a1079b27ba85"
|
||||
|
||||
[[package]]
|
||||
name = "v8"
|
||||
version = "0.106.0"
|
||||
version = "129.0.0"
|
||||
dependencies = [
|
||||
"align-data",
|
||||
"bindgen",
|
||||
|
@ -1,6 +1,6 @@
|
||||
[package]
|
||||
name = "v8"
|
||||
version = "0.106.0"
|
||||
version = "129.0.0"
|
||||
description = "Rust bindings to V8"
|
||||
readme = "README.md"
|
||||
authors = ["the Deno authors"]
|
||||
|
16
README.md
16
README.md
@ -30,6 +30,18 @@ V8 Version: 12.9.202.18
|
||||
Due to the complexity and size of V8's build, this is nontrivial. For example
|
||||
the crate size must be kept under 10 MiB in order to publish.
|
||||
|
||||
## Versioning
|
||||
|
||||
Rusty V8's major version aligns with Chrome's major version, which corresponds
|
||||
to a specific V8 release. For example, Rusty V8 `129.0.0` maps to Chrome
|
||||
`129.x.y.z`, which uses V8 `12.9.a.b`. While the minor and patch numbers between
|
||||
Chrome and V8 may differ, Rusty V8 will follow Chrome's release schedule, with a
|
||||
new major version every 4 weeks.
|
||||
|
||||
As a Rust crate, Rusty V8 follows semantic versioning (semver) and will not
|
||||
introduce breaking changes within a major version. However, major version bumps
|
||||
will occur regularly to stay in sync with Chrome's release cycle.
|
||||
|
||||
## Binary Build
|
||||
|
||||
V8 is very large and takes a long time to compile. Many users will prefer to use
|
||||
@ -115,7 +127,9 @@ For Mac builds: You'll need Xcode and Xcode CLT installed. Recent macOS versions
|
||||
will also require you to pass PYTHON=python3 because macOS no longer ships with
|
||||
`python` simlinked to Python 3.
|
||||
|
||||
For Android builds: You'll need to cross compile from a x86_64 host to the aarch64 or x64 android. You can use the following commands:
|
||||
For Android builds: You'll need to cross compile from a x86_64 host to the
|
||||
aarch64 or x64 android. You can use the following commands:
|
||||
|
||||
```bash
|
||||
rustup target add aarch64-linux-android # or x86_64-linux-android
|
||||
V8_FROM_SOURCE=1 cargo build -vv --target aarch64-linux-android
|
||||
|
Loading…
Reference in New Issue
Block a user