-
Notifications
You must be signed in to change notification settings - Fork 321
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
Can't build from git checkout without V8_FROM_SOURCE=1
#1634
Comments
You will need to specify |
thanks, but what I want is to build with the .a (v8 library). By what setting will this repo built with the binary form of v8 library? From what I read from the readme, it should be default. Anything that I missed? |
@devsnek can you take a look? |
@felixf4xu if you're building with a pre-existing |
Thanks, I guess I was confused by the readme:
Anyway, I would like to share my steps to build this repo.
V8_FROM_SOURCE=1 cargo build This will fail after a lot of c++ errors which is not a surprise, but it will create the [v8 129.0.0] cargo:rustc-env=RUSTY_V8_SRC_BINDING_PATH=/home/ccc/github/rusty_v8/target/debug/gn_out/src_binding.rs
V8_FROM_SOURCE=0 RUSTY_V8_SRC_BINDING_PATH=/home/ccc/github/rusty_v8/target/debug/gn_out/src_binding.rs cargo build it will build successfully very fast, because Then I can go on to try the examples by But this building process makes me wonder, if only /* automatically generated by rust-bindgen 0.69.4 */ Option 1: Option 2: |
I also hit this issue - the onboarding is really confusing - should the |
src_binding.rs is target and build configuration specific, so it can´t be easily checked in. If you're building from the git repo the only officially supported way is with |
cargo build
V8_FROM_SOURCE=1
@devsnek could you adjust the README? This section is really confusing, as it implies that
|
Hi,
I cloned this repo and its submodules, then in the root folder of the repo, I run
cargo build
I'm not sure if this is the right first step to build.
I did not set any env variable.
The text was updated successfully, but these errors were encountered: