llvm dev - Dec 2020 - LLVMBuild is gone (which is a good thing)

I just did a pull of the tagged 11.0.1 and the build system had changed.
LLVMBuild is gone and now everything is done with CMake now. This is great,
really.

However, the error messages I got from the new build were confusing to say
the least. Would it be possible for CMake to check for the mere existence
of an LLVMBuild.txt in the backend directories and fail with an error to
upgrade to the new build system?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20201203/124a09fc/attachment.html>

Am Do., 3. Dez. 2020 um 11:45 Uhr schrieb Chris Sears via llvm-dev
<llvm-dev at lists.llvm.org>:
> I just did a pull of the tagged 11.0.1 and the build system had changed.
LLVMBuild is gone and now everything is done with CMake now. This is great,
really.
Thank Serge (added to CC)  who did all the work: https://reviews.llvm.org/D90848

> However, the error messages I got from the new build were confusing to say
the least. Would it be possible for CMake to check for the mere existence of an
LLVMBuild.txt in the backend directories and fail with an error to upgrade to
the new build system?
To clarify: You have a downstream backend that does not work anymore
because the dependencies now have to be encoded in the
add_llvm_component_library call the LLVMBuild.txt is ignored?

You could upload a patch to Phabricator. However, since your backend
has now updated, this doesn't seem useful to you anymore (, but maybe
for others)

Michael

On 12/3/20 9:44 AM, Chris Sears via llvm-dev wrote:
> I just did a pull of the tagged 11.0.1 and the build system had changed. 
> LLVMBuild is gone and now everything is done with CMake now. This is 
> great, really.
> 
Are you sure you pulled 11.0.1 ? LLVMBuild.txt was removed in trunk 
after the release/11.x branch was made.

-Tom
> However, the error messages I got from the new build were confusing to 
> say the least. Would it be possible for CMake to check for the mere 
> existence of an LLVMBuild.txt in the backend directories and fail with 
> an error to upgrade to the new build system?
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>