spkg-configure.m4 for cmake

[dimpase]

practically a copy of the one for patch

Depends on #27662

CC: @embray @kiwifb @slel @vinklein

Component: packages: optional

Author: Dima Pasechnik

Branch/Commit: 741de68

Reviewer: Erik Bray, Samuel Lelièvre, Vincent Delecroix

Issue created by migration from https://trac.sagemath.org/ticket/27487

[embray]

comment:2

Well, this system's cmake is < 3.11, so in this case it "worked" in that it refused to use my system cmake. I don't know how strict the 3.11 requirement is but I'm fine with leaving it for now.

I'll also test on a system with a newer cmake.

[embray]

comment:3

Apparently 3.11 is actually quite recent. Unless there's a specific need for it, let's try setting to just 3.0 and see how that goes (my Cygwin has 3.83.6.2 for example).

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

07b87cf

spkg-configure for cmake

[sagetrac-git]

Changed commit from bd93208 to 07b87cf

[dimpase]

comment:5

OK, now it's 3.0.

[dimpase]

comment:6

Are you still checking this? There is an extra complication here that cmake
keeps 3.x for long, issuing updates with numbers 3.x.y to them on a regular basis.
Perhaps it's better to go all the way to x big enough for the meaningful cases such as current cygwin etc.

[embray]

comment:7

Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually)

[slel]

comment:8

Note: we upgraded to cmake 3.11.0 in #25109 because cmake 3.8.1 was
not enough to build primecount 4.3 (an optional package).

However, primecount 4.6 was released on 2019-04-13 and lowered the
requirement from cmake 3.9 to cmake 3.4, if I understand correctly.