[llvm-dev] llvm-config deprecation (original) (raw)
Andrew Kelley via llvm-dev llvm-dev at lists.llvm.org
Tue Jan 1 20:22:50 PST 2019
- Previous message: [llvm-dev] llvm-config deprecation
- Next message: [llvm-dev] llvm-config deprecation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1/1/19 10:00 PM, Chandler Carruth wrote:
Not sure why you're getting the CMake error, but we aren't deprecating
llvm-config
that I know of.The message you're seeing is about deprecating the use of
llvm-config
from CMake. There, we are providing installed CMake fragments that we want people to use instead of relying on the genericfoo-config
support in CMake combined withllvm-config
. Much as your email explain, there are many (non-CMake) users ofllvm-config
and it would be strange for it to go away.
Thanks for the clarification. In this case, all is well. I believe that what I am observing is the "out-of-tree" build process, where LLVM and Clang are installed via separate source tarballs, which produces this warning. I do think that it would be beneficial to improve the wording of the warning to clarify that llvm-config is not deprecated, as well as to fix "out of tree" build to not produce the warning - since this message would be displayed for package managers such as Debian when building Clang for the system, and this is likely to cause confusion.
Regards, Andrew
-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190101/b21362b6/attachment.sig>
- Previous message: [llvm-dev] llvm-config deprecation
- Next message: [llvm-dev] llvm-config deprecation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]