Displaying 4 results from an estimated 4 matches for "llvmconfiglib".
Did you mean:
llvmconfiglibs
2014 Sep 09
2
[LLVMdev] Can't build against LLVM-3.5 with CMake: CMakeExports.cmake broken?
...hy we taught cmake/modules/Makefile to generate LLVMConfig.cmake
and LLVMExports.cmake.
> What is happening is that none of the libraries are being added into
> LLVMExports.cmake file when it is generated by ``cmake/modules/Makefile``.
[snip]
> One way to "fix" this is make sure LLVMConfigLibs is also set when
> using --enable-shared as the attached patch does.
The patch works for me and is likely sufficient at least for a fixup
during distro packaging and perhaps also in the 3.5 release branch.
Making the shared library itself available as an imported target is
a separate problem...
2014 Sep 09
3
[LLVMdev] Can't build against LLVM-3.5 with CMake: CMakeExports.cmake broken?
Hi,
I can't reproduce your issue on the LLVM 3.5 release branch or trunk
it. Looking at your bug report I think your install is messed up
```
CMake Error at /usr/local/Cellar/llvm/HEAD/share/llvm/cmake/LLVMExports.cmake:6
(set_property):
set_property could not find TARGET LLVMSupport. Perhaps it has not yet
been created.
Call Stack (most recent call first):
2014 Sep 09
2
[LLVMdev] Can't build against LLVM-3.5 with CMake: CMakeExports.cmake broken?
On 09/09/2014 01:53 PM, Dan Liew wrote:
>> It looks like LLVMConfigLibs was created in r112714 for local use in
>> Makefile.rules. The only use outside Makefile.rules is now in
>> cmake/modules/Makefile. Teaching cmake/modules/Makefile to do
>> a direct invocation would be fine with me.
>
> Okay. Attached is a patch that does this. Does this...
2014 Sep 10
2
[LLVMdev] Can't build against LLVM-3.5 with CMake: CMakeExports.cmake broken?
On Sep 9, 2014, at 7:12 AM, Dan Liew <dan at su-root.co.uk> wrote:
> This is happening because the ``LLVMConfigLibs`` makefile variable is
> empty when used in ``cmake/modules/Makefile``. It is normally set in
> Makefile.rules . However if you build with --enable-shared this
> variable doesn't get set and so LLVMExports.cmake isn't generated
> correctly.
>
> @David: Were you also comp...