aaronpuchert added a comment. In D129160#3721943 <https://reviews.llvm.org/D129160#3721943>, @isuruf wrote:
> Sure. If an application links to `libclang.so` when the application is being > built, the application will hardcode `libclang.so.13` in it and will look for > it. > When the SONAME changes to `libclang.so.15` in LLVM 15, the application will > not be able to use the libclang from LLVM 15 unless the > application was rebuilt with `libclang.so` in LLVM 15. That's the problem **after** this change, but what was the problem before the change? The commit message (where my quote is from) suggests this wouldn't have worked even if we stayed at `libclang.so.13` in LLVM 15. 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
