Automatically discover location of libclang
#78
Milestone
Comments
|
Not sure if we should use a custom For more information on the new Hooks API, see @sheaf 's talk and the corresponding examples. |
|
|
Merged
phadej
added a commit
that referenced
this issue
Aug 21, 2024
Resolves #78. Having C-dependencies in a separate package work-around unclear behavior of `build-type: Configure` which seems to add extra definitions to the main library only (`a-lib.buildinfo`; possibly we can have extra buildinfos for other components too, but the file naming scheme is mysterious). On the other hand, separate package for `libclang` bindings might be a good idea anyway. It's a separate self-contained functionality, and e.g. `clang-tutorial` depends on that only (and could be pulled into separate package as well, not to pollute the main thing).
phadej
added a commit
that referenced
this issue
Aug 21, 2024
Resolves #78. Having C-dependencies in a separate package work-around unclear behavior of `build-type: Configure` which seems to add extra definitions to the main library only (`a-lib.buildinfo`; possibly we can have extra buildinfos for other components too, but the file naming scheme is mysterious). On the other hand, separate package for `libclang` bindings might be a good idea anyway. It's a separate self-contained functionality, and e.g. `clang-tutorial` depends on that only (and could be pulled into separate package as well, not to pollute the main thing).
phadej
added a commit
that referenced
this issue
Aug 21, 2024
Resolves #78. Having C-dependencies in a separate package work-around unclear behavior of `build-type: Configure` which seems to add extra definitions to the main library only (`a-lib.buildinfo`; possibly we can have extra buildinfos for other components too, but the file naming scheme is mysterious). On the other hand, separate package for `libclang` bindings might be a good idea anyway. It's a separate self-contained functionality, and e.g. `clang-tutorial` depends on that only (and could be pulled into separate package as well, not to pollute the main thing).
phadej
added a commit
that referenced
this issue
Aug 21, 2024
Resolves #78. Having C-dependencies in a separate package work-around unclear behavior of `build-type: Configure` which seems to add extra definitions to the main library only (`a-lib.buildinfo`; possibly we can have extra buildinfos for other components too, but the file naming scheme is mysterious). On the other hand, separate package for `libclang` bindings might be a good idea anyway. It's a separate self-contained functionality, and e.g. `clang-tutorial` depends on that only (and could be pulled into separate package as well, not to pollute the main thing).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unfortunately,
libclangdoes not supportpkg-config(llvm/llvm-project#9777).clang-pureuses a custom setup script which callsllvm-config, we might consider doing something similar. For now, we simply depend on something like this incabal.project:The text was updated successfully, but these errors were encountered: