[llvm-dev] RFC: Updating to CMake 3.15.0
Michael Kruse via llvm-dev
llvm-dev at lists.llvm.org
Sun Nov 3 21:35:14 PST 2019
Am So., 3. Nov. 2019 um 18:20 Uhr schrieb Neil Nelson via llvm-dev
<llvm-dev at lists.llvm.org>:
> Glad we are getting some reasonable justifications for CMake 3.15.0. There are two points we may be missing.
> Is our plan to just keep updating to the most recent CMake version or will our objectives be reached with this version? If we gain what we need with this version then after a while we will have the Ubuntu LTS aligned.
> For my current purposes, LLVM can get wild without much worry here. I just clone a VM and run what is useful and then delete it. A bit like use once and throw away. This is not for production purposes but for getting a better view of software structure that LLVM can provide.
> When I was managing IT and the servers for a small company that needed to be live 24/7 we used the latest Ubuntu LTS version because we needed rock-solid performance as best we could get. The software in the LTS version is tested and used by a large user base with necessary updates and so we expected to have high reliability.
> Those saying how easy it was to obtain the latest CMake have apparently not been faced with the absolute need for solid up-time. Installing hack-me-now, buggy, bleeding-edge software was severely discouraged. But in the LLVM environment, I can see where that is not a strong necessity.
> But at the same time, does LLVM strive to be the backbone of 24/7 software? Or is it more of a cool thing with some interesting code analysis properties? I suspect its nature is a bit wild, bleeding edge. And that's OK.
You are using LTS versions for reliability, but then expect the
development version of LLVM to be just as stable for your 24/7
More information about the llvm-dev