Hi Kyle,
* Kyle Edwards [2023-06-19 09:18]:
CMake upstream here. We do have a tutorial that we've put together and
improved over the last few years that teaches modern CMake and avoids
using the old directory-level commands. You can find it here:
https://cmake.org/cmake/help/latest/guide/tuto
On 6/17/23 12:29, Timo Röhling wrote:
Being backwards compatible is CMake's greatest blessing and greatest
curse at the same time, because people still run into crappy,
20 year old tutorials and needlessly complicated (but working) code
snippets from CMake 2.x on the Internet, making them believ
Hi David,
* David Kalnischkies [2023-06-17 13:23]:
fwiw apt would trigger this in its autopkgtest as one of them (the
main run-tests) builds a sub-directory of helpers with cmake via the
main "upstream" CMakeList.txt file. That test is allowed to have stderr
output through, so no problem on tha
On Fri, Jun 16, 2023 at 01:08:08AM +0200, Timo Röhling wrote:
> Attached is a list of most likely affected packages, which
> I generated with a code search for
>
> (?i)cmake_minimum_required\s*\(\s*version\s*(?:3\.[01234]|2)(?:[.)]|\s)
fwiw apt would trigger this in its autopkgtest as one of
Hi,
this is an advance notice that CMake 3.27, scheduled for July 2023,
will begin issuing a deprecation warning if a script requests
backwards compatibility to versions older than 3.5.
CMake will remain backwards compatible, but autopkgtests may break
due to stderr output. If you build tests wi
5 matches
Mail list logo
