-
Notifications
You must be signed in to change notification settings - Fork 316
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
bindgen does not use downloaded chromium clang #1595
Comments
The above comment asking you to download a file is malware to steal your account; do not under any circumstances download or run it. The post needs to be removed. If you have attempted to run it please have your system cleaned and your account secured immediately. |
I wonder if we need to set up bindgen to look in the right place for clang. Could you try temporarily setting |
@devsnek Thanks for your answer. After I looked through the doc of bindgen. And I installed clang with Although it has been successfully compiled, I‘m confused about some issues. |
I looked into this some more and it turns out that the clang we download from chromium does not include libclang shared libraries. I'm discussing with them whether these can be included, in which case it should be fairly trivial to set up |
Since v0.95.0, a new feature #1507 has been merged.
I got some errors when compiling v8.
Error message:
This error occurs in v8 build.rs running
build_binding
.I guess this is because bindgen denps on clang, but I haven't configured it.
My build host is WSL Ubuntu 22.04.
My build steps are as follows:
V8_FROM_SOURCE=1 cargo build -vv
.This set of steps works before v0.94.0.
Acctually, I was able to build successfully in github action.
So I think this may be caused by my environment not being configured.
At first I wanted to build for Android, I encountered a problem that the header file could not be found.
Then I tired build for x86_64-unknown-linux-gnu, I encountered the similar problem.
According to README:
Clang can be automatically downloaded and configured.
Maybe the new version need to configure clang?
The text was updated successfully, but these errors were encountered: