Skip to content

Commit 6a2ee57

Browse files
authored
Merge pull request #80 from well-typed/tcard/manual
Update `llvm-config` documentation
2 parents 4570986 + b10b313 commit 6a2ee57

1 file changed

Lines changed: 9 additions & 7 deletions

File tree

manual/README.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -94,15 +94,17 @@ script, which determines which `libclang` shared library is linked.
9494
The `llvm-config` program, generally included in LLVM/Clang installations, is
9595
used to configure software builds to use a specific LLVM/Clang installation.
9696
The `libclang-bindings` configure script uses it to determine the include and
97-
library directories. If you have more than one version of LLVM/Clang installed,
98-
you can configure your `PATH` to ensure that the `llvm-config` for the version
99-
that you want to use is found.
97+
library directories. In some cases, you may need to configure your `PATH`
98+
environment variable to ensure that the `llvm-config` for the version that you
99+
want to use is found.
100100
101101
> [!NOTE]
102-
> Some platforms provide versioned executables of `llvm-config` (e.g., Fedora
103-
> with `clangNN-devel` provides `llvm-config-NN`). Ensure an unversioned
104-
> executable is available (e.g., by installing `clang-devel`, or by linking
105-
> `llvm-config-NN` to `llvm-config` on Fedora).
102+
> Many Linux distributions provide packages for multiple versions of LLVM/Clang.
103+
> If you install the current version, `llvm-config` should work without any
104+
> configuration. If you install an older version, you likely need to update your
105+
> `PATH` to prepend the `bin` directory for that version. Run
106+
> `llvm-config --version` and `clang --version` to confirm that you have the
107+
> desired version configured.
106108
107109
### Using `LLVM_PATH`
108110
[t:using-llvm-path]: #using-llvm_path

0 commit comments

Comments
 (0)