Describe the bug
- llvm-config sees LLVM’s root directory as
<vcpkg path>/packages/llvm_x64-windows-static/tools
- i.e. the command
llvm-config --includedir incorrectly returns the value <vcpkg path>/packages/llvm_x64-windows-static/tools/include
- The following also return incorrect values:
llvm-config --libdir
llvm-config --bindir
llvm-config --obj-dir
- etc.
- See https://releases.llvm.org/8.0.0/docs/CommandGuide/llvm-config.html for a complete list of flags
Environment
- OS: tested on Windows and macOS (probably applies to Linux as well)
- Compiler: revision current
To Reproduce
Steps to reproduce the behavior:
vcpkg install llvm:x64-windows-static
llvm:x64-osx on macOS
- takes several hours to build
cd packages/llvm_x64-windows-static/tools/llvm
llvm-config --includedir
Expected behavior
- llvm-config should see its root directory as
<vcpkg path>/packages/llvm_x64-windows-static
- i.e.
llvm-config --includedir should return <vcpkg path>/packages/llvm_x64-windows-static/include
Failure logs
None
Additional context
vcpkg currently uses the option -DLLVM_TOOLS_INSTALL_DIR=tools/llvm to set the install directory. I’m not sure if LLVM even has options to set include, lib, etc. directories.
Describe the bug
<vcpkg path>/packages/llvm_x64-windows-static/toolsllvm-config --includedirincorrectly returns the value<vcpkg path>/packages/llvm_x64-windows-static/tools/includellvm-config --libdirllvm-config --bindirllvm-config --obj-dirEnvironment
To Reproduce
Steps to reproduce the behavior:
vcpkg install llvm:x64-windows-staticllvm:x64-osxon macOScd packages/llvm_x64-windows-static/tools/llvmllvm-config --includedirExpected behavior
<vcpkg path>/packages/llvm_x64-windows-staticllvm-config --includedirshould return<vcpkg path>/packages/llvm_x64-windows-static/includeFailure logs
None
Additional context
vcpkg currently uses the option
-DLLVM_TOOLS_INSTALL_DIR=tools/llvmto set the install directory. I’m not sure if LLVM even has options to set include, lib, etc. directories.