Closed deech closed 7 years ago
Bump.
Hey, sorry this has taken so long. Will work on this over the weekend.
Forcing every end user to have a specific llvm version, getting it recognized, and making sure it's built with the right flags is an extreme pain point.
Because of this, while this library is awesome, it's just not practical to depend on it at all. No widely used library can afford to depend on something that's basically going to break on every single user's machine without significant manual intervention. (Imagine how many people would use lens if every user no matter how naive had to go through this?)
Would it be possible to go back to building llvm at compile time? High compile times are annoying but at least they make the library practical. How about instead automatically downloading and using official llvm binaries for platforms on which these already exist?
Andrei
On May 25, 2017 2:11 PM, "Chetan Taralekar" notifications@github.com wrote:
Hey, sorry this has taken so long. Will work on this over the weekend.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/chetant/LibClang/pull/66#issuecomment-304082007, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQxII4_6IzdY5Y9MFiETu08vCU7isFuks5r9cRLgaJpZM4NK7pV .
Sorry to keep pestering but please let me know if there is an issue with the PR. Thanks!
I've added support for static linking in the form of a flag
staticbuild
. Like the previous version setting this flag will concatenate all the LLVM, Clang and Haskell bindings libraries into one big archive (63MB on my machine). However unlike the previous version LLVM and Clang are not cloned and built, instead it is assumed that the user has static versions of those libraries at the location specified byllvm-config --libdir
.Help building and testing this on various versions of OSX and Linux is appreciated.
/cc @abarbu