Ryan Dahl
Ryan Dahl
I've landed #700 which works around this issue by reverting v8/v8@7f9d7f0. This is a fine stop-gap, but in the long-run it is untenable for us to float patches like this.
duplicate of #49
gn mistakenly thinks the host is x86_64 (I think because we use x86_64 gn binaries). To force arm64 build use ``` V8_FROM_SOURCE=1 GN_ARGS="host_cpu=\"arm64\"" cargo build -vv ```
Not supported in CI yet, but I've uploaded aarch64-apple-darwin binaries for v0.14.0 https://github.com/denoland/rusty_v8/releases/tag/v0.14.0
We don't have any explicit plans yet, but we want to do this. Half of the problem rusty_v8 solves is providing build system integration between gn and cargo and providing...
Yes I think so too. Tho I think this should probably be dealt with at the rusty v8 layer...
Probably we should use asan instead of valgrind (due to slowness) https://doc.rust-lang.org/beta/unstable-book/compiler-flags/sanitizer.html
What do you need this for?
The OSX equivalent of `--gc-sections` is `-dead_strip`. Apparently enabled when then `symbol_level == 2`. https://source.chromium.org/chromium/chromium/src/+/master:build/config/compiler/BUILD.gn;l=1970?q=gc-sections&ss=chromium%2Fchromium%2Fsrc When I remove [our override for symbol_level](https://github.com/denoland/rusty_v8/blob/master/.gn#L36 ), I see that `-dead_strip` gets enabled for...
Can you provide example code that demonstrates this?