aaronpuchert added a comment. > Also, this change did not really acheive it's purpose of allowing apps to use > newer versions of libclang.so without rebuilding, because a new version of > libclang.so requires a new version of libLLVM.so, which does not have a > stable ABI.
Could you elaborate on this? If an application uses only `libclang.so`, and that is updated to a newer version using a newer `libLLVM.so`, why would the application need to be rebuilt? Isn't the C API self-contained? It was a bit tough to decouple `libclang.so` packaging-wise, but we released it like that already and reverting now seems to just obsolete efforts that had already happened. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D129160/new/ https://reviews.llvm.org/D129160 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
