mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-26 11:45:37 +00:00
985a376afa
The current setup for bindgen relies on either finding clang/libclang from the output of llvm-config, or from the paths given via the configure flags --with-clang-path/--with-libclang-path. One _very_ common problem is that the llvm-config we end up using does not correspond to the clang used for compilation, which has some undesirable side effect, like failing to build. So instead of relying on llvm-config, we do the following: - when the compiler is clang, we just use that - when the compiler is clang-cl, we use clang from the same directory - otherwise, we either try to find clang in PATH, or rely on --with-clang-path. Once clang is found, we try to deduce the location of the corresponding libclang via the output of `clang -print-search-dirs`, or rely on --with-libclang-path. Differential Revision: https://phabricator.services.mozilla.com/D33241 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| android-ndk.configure | ||
| android-sdk.configure | ||
| arm.configure | ||
| bindgen.configure | ||
| checks.configure | ||
| compile-checks.configure | ||
| compilers-util.configure | ||
| flags.configure | ||
| headers.configure | ||
| init.configure | ||
| java.configure | ||
| keyfiles.configure | ||
| memory.configure | ||
| node.configure | ||
| old.configure | ||
| pkg.configure | ||
| rust.configure | ||
| toolchain.configure | ||
| tup.configure | ||
| util.configure | ||
| warnings.configure | ||
| windows.configure | ||