search for: ltses

...13.4, and so I suggest we upgrade to that. Here's a proposed process: >>> >>> 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying that CMake 3.13.4 will be the new minimum version starting with LLVM 12.0.0, and mentioning the versions used in various LTSes. >>> 2. Immediately send a courtesy heads-up email to all build-bot owners telling them about the upcoming change. >>> 3. Right after we branch off the release branch for LLVM 11.0.0 (the next one), make the minimum CMake version required be 3.13.4. >>> 4. Iterate on (3)...

....13.4, and so I suggest we upgrade to that. Here's a proposed process: >>> >>> 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying that CMake 3.13.4 will be the new minimum version starting with LLVM 12.0.0, and mentioning the versions used in various LTSes. >>> 2. Immediately send a courtesy heads-up email to all build-bot owners telling them about the upcoming change. >>> 3. Right after we branch off the release branch for LLVM 11.0.0 (the next one), make the minimum CMake version required be 3.13.4. >>> 4. Iterate on (3)...

...tributions be 3.13.4, and so I suggest we upgrade to that. Here's a proposed process: > > 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying that CMake 3.13.4 will be the new minimum version starting with LLVM 12.0.0, and mentioning the versions used in various LTSes. > 2. Immediately send a courtesy heads-up email to all build-bot owners telling them about the upcoming change. > 3. Right after we branch off the release branch for LLVM 11.0.0 (the next one), make the minimum CMake version required be 3.13.4. > 4. Iterate on (3) until all bots are migra...

...; that. Here's a proposed process: >> >>> >> >>> 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt >> saying that CMake 3.13.4 will be the new minimum version starting with LLVM >> 12.0.0, and mentioning the versions used in various LTSes. >> >>> 2. Immediately send a courtesy heads-up email to all build-bot owners >> telling them about the upcoming change. >> >>> 3. Right after we branch off the release branch for LLVM 11.0.0 (the >> next one), make the minimum CMake version required be 3.1...

...completely-trivial instructions on how to get, build, and use a new version for building LLVM (WITHOUT having to install it!), should both suffice -- and is more likely to be useful. I do NOT think we should have a policy tying ourselves to versions supported by certain LTS releases. Users of such LTSes can download a newer cmake. We should, of course, strive to not be unnecessarily annoying -- even though the amount of work to download a new version is small, it's not zero. We should _consider_ the versions that developers are likely to have pre-installed on their machines, and drop support f...

...or LTS distributions be 3.13.4, and so I suggest we upgrade to that. Here's a proposed process: 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying that CMake 3.13.4 will be the new minimum version starting with LLVM 12.0.0, and mentioning the versions used in various LTSes. 2. Immediately send a courtesy heads-up email to all build-bot owners telling them about the upcoming change. 3. Right after we branch off the release branch for LLVM 11.0.0 (the next one), make the minimum CMake version required be 3.13.4. 4. Iterate on (3) until all bots are migrated. 5. Send a...

...or LTS distributions be 3.13.4, and so I suggest we upgrade to that. Here's a proposed process: 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying that CMake 3.13.4 will be the new minimum version starting with LLVM 12.0.0, and mentioning the versions used in various LTSes. 2. Immediately send a courtesy heads-up email to all build-bot owners telling them about the upcoming change. 3. Right after we branch off the release branch for LLVM 11.0.0 (the next one), make the minimum CMake version required be 3.13.4. 4. Iterate on (3) until all bots are migrated. 5. Send a...

...completely-trivial instructions on how to get, build, and use a new version for building LLVM (WITHOUT having to install it!), should both suffice -- and is more likely to be useful. I do NOT think we should have a policy tying ourselves to versions supported by certain LTS releases. Users of such LTSes can download a newer cmake. We should, of course, strive to not be unnecessarily annoying -- even though the amount of work to download a new version is small, it's not zero. We should _consider_ the versions that developers are likely to have pre-installed on their machines, and drop support f...

...o get, build, and > use a new version for building LLVM (WITHOUT having to install > it!), should both suffice -- and is more likely to be useful. > > I do NOT think we should have a policy tying ourselves to versions > supported by certain LTS releases. Users of such LTSes can > download a newer cmake. We should, of course, strive to not be > unnecessarily annoying -- even though the amount of work to > download a new version is small, it's not zero. We should > _consider_ the versions that developers are likely to have > pre-in...

...suggest we upgrade to that. Here's a proposed > process: > > 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt > saying that CMake 3.13.4 will be the new minimum version starting > with LLVM 12.0.0, and mentioning the versions used in various LTSes. > > 2. Immediately send a courtesy heads-up email to all build-bot > owners telling them about the upcoming change. > > 3. Right after we branch off the release branch for LLVM 11.0.0 > (the next one), make the minimum CMake version required be 3.13.4. > >...

...or LTS distributions be 3.13.4, and so I suggest we upgrade to that. Here's a proposed process: 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying that CMake 3.13.4 will be the new minimum version starting with LLVM 12.0.0, and mentioning the versions used in various LTSes. 2. Immediately send a courtesy heads-up email to all build-bot owners telling them about the upcoming change. 3. Right after we branch off the release branch for LLVM 11.0.0 (the next one), make the minimum CMake version required be 3.13.4. 4. Iterate on (3) until all bots are migrated. 5. Send a...

...completely-trivial instructions on how to get, build, and use a new version for building LLVM (WITHOUT having to install it!), should both suffice -- and is more likely to be useful. I do NOT think we should have a policy tying ourselves to versions supported by certain LTS releases. Users of such LTSes can download a newer cmake. We should, of course, strive to not be unnecessarily annoying -- even though the amount of work to download a new version is small, it's not zero. We should _consider_ the versions that developers are likely to have pre-installed on their machines, and drop support f...

...or LTS distributions be 3.13.4, and so I suggest we upgrade to that. Here's a proposed process: 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying that CMake 3.13.4 will be the new minimum version starting with LLVM 12.0.0, and mentioning the versions used in various LTSes. 2. Immediately send a courtesy heads-up email to all build-bot owners telling them about the upcoming change. 3. Right after we branch off the release branch for LLVM 11.0.0 (the next one), make the minimum CMake version required be 3.13.4. 4. Iterate on (3) until all bots are migrated. 5. Send a...

...>> that. Here's a proposed process: >> >> >> >> 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying >> that CMake 3.13.4 will be the new minimum version starting with LLVM >> 12.0.0, and mentioning the versions used in various LTSes. >> >> 2. Immediately send a courtesy heads-up email to all build-bot owners >> telling them about the upcoming change. >> >> 3. Right after we branch off the release branch for LLVM 11.0.0 (the next >> one), make the minimum CMake version required be 3.13.4. &gt...

...3.13.4, and so I suggest we upgrade to that. Here's a proposed process: > > > > 1. Immediately add a CMake warning in <root>/llvm/CMakeLists.txt saying that CMake 3.13.4 will be the new minimum version starting with LLVM 12.0.0, and mentioning the versions used in various LTSes. > > 2. Immediately send a courtesy heads-up email to all build-bot owners telling them about the upcoming change. > > 3. Right after we branch off the release branch for LLVM 11.0.0 (the next one), make the minimum CMake version required be 3.13.4. > > 4. Iterate on (3) until...

We had this discussion a few months ago and it petered out, and it’s recently been revived in the context of upgrading the CMake version specifically for libc++ (at which point people suggested upgrading the CMake version used by all of LLVM), so let’s try to move this forward. Our current required minimum version is CMake 3.4.3, which was released on January 25th 2016. It’s interesting to note

Yeah, I don’t anticipate Windows posing problems. Also, it’s pretty common in Windows to just install software yourself, and CMake ships prebuilt binaries and an installer, so it’s pretty easy to get set up with it. Chris, I’m gonna reiterate a question of mine from an earlier email, since you may have thoughts on it: * If we want to limit ourselves to CMake versions supported by LTS releases of