- User Since
- Sep 28 2015, 2:26 AM (224 w, 4 d)
Aug 16 2018
Yes, someone please commit this for me.
Aug 8 2018
Aug 7 2018
Does this make sense or could it cause issues with other modules? I haven't thought of possible implications, but it seems to work OK when tested on top of LLVM 6.0.1.
May 10 2018
Apologies for the random a-year-later comment, but how does this relate to D31524 (which already seems to version libLLVM.so's symbols)?
Mar 13 2018
You have a point that any further tweaks to llvm_config should be created and reviewed separately. What I described above is not too great either; it shouldn't be required to specify USE_SHARED.
+1 from me; it fixes llvm_config(foo USE_SHARED ...) for out-of-tree builds.
Mar 12 2018
One more observation: It might be preferable to avoid defining set(LLVM_DYLIB_COMPONENTS all) in non-DYLIB builds. It prevents llvm_config(foo USE_SHARED ...) from opportunistically linking to the DYLIB while still having the static libraries as a fallback.
Scratch that, I see what's going on! The body of the llvm_config macro needs to check if(ARG_USE_SHARED) instead of if(USE_SHARED).
This change seems to make llvm_config() usable for out-of-tree builds, neat! I tried a standalone build of LLDB and it works fine after having rebuilt llvm with this change.
May 7 2016
Jan 15 2016
The latest patch still applies (relatively cleanly) to Clang 3.7.x which is nice. The infinite recursion segfaults appear to be gone, thanks!
Dec 26 2015
Dec 16 2015
We have received a few reports of clang crashes after applying the abi_tag support patch to our llvm/clang package in Arch Linux.
Oct 1 2015
Sep 28 2015
Thanks for the review.
Just a note that this change is specific to CMake since autotools already installs clang-query (along with some other tools).