[LLVMdev] [RFC] Raise minimum required CMake version to 3.0

Tobias Grosser tobias at grosser.es
Tue Mar 10 12:29:59 PDT 2015

On 03/10/2015 06:38 PM, Mehdi Amini wrote:
> Hi Tobias,


>>> Also, could we just limit the cmake version on windows builds? In the
>>> end on linux cmake 2.8.9 works great.
>> Rafael asked if updating the bot is not an option. It indeed is an option, but requires cmake to be manually downloaded and installed instead of using the available packages.
>> This is OK for one bot, but it will add complications for everybody who uses debian and wants to install LLVM. It also will make it more complicated to move to a fully cmake based build as all such debian based buildbots would require a manual installation of cmake (I have 12 more of these).
>> Before doing so I wanted to understand if it is indeed intended to require debian-stable users to *manually* install and manage cmake or if there is not a lower overhead version. Can this bug not be fixed for windows without complicating live for debian users?
> In light of the list of new features that Chris listed, and considering that Debian 8 is frozen (RC1 already shipped in January) and should be released before the next LLVM version (but who knows with Debian…), do you have a plan to update CMake on all your bots? Or do you still have strong other concerns?

The cmake based systems I am running are updated to 3.0. No need to 
worry about my buildbots.

Chandler previously asked to ensure we stay with a cmake version that is 
available in the Ubuntu packages. If you want to drop this requirement, 
you probably want to cross-check with him.

I personally also believe being a little bit more conservative here 
would be nice, if possible, as it keeps the barrier of entry to LLVM 
lower and also makes moving away from autoconf easier. I suggest that we 
check with Sylvestre if his apt-get builds for ubuntu LTS will keep 
working with cmake 3.0 (after autoconf support has dropped).

Maybe I am over careful here. If I am the only one that conservative, 
feel free to move ahead.


More information about the llvm-dev mailing list