Also some of our Jenkins build server slaves can't build any more due to
the minimum required CMake version change.
Ubuntu 16.04 just has CMake 3.5 in it's repo, CentOS 7 just 2.8, and one of
the macOS slaves is at 3.2 (is there such a thing as a repository on
MacOS?).
As long as there's no real functional requirement for CMake above 2.8, I'd
vote for reversing the minimum requirement change back to 2.8.
On Wed, Aug 1, 2018 at 4:34 PM, Rony G. Flatscher <rony.flatsc...@wu.ac.at>
wrote:
> An update to the minimum version number. While trying to create ooRexx
> 5.0beta on Ubuntu I noticed that only version 3.5 was available there as of
> yesterday, which could not be used to build ooRexx as its minimum CMake
> level is set to 3.8. (Went to cmake.org and downloaded the latest version
> for Linux from there which successfully built ooRexx.)
>
> The question would be whether it would be possible to use as minimum 3.5,
> such that "bread-and-butter"-Linux systems could be used to build ooRexx
> (thinking of zLinux, not knowing how up-to-date their cmake would be).
>
> ---rony
>
> On 15.07.2018 08:36, Mark L. Gaubatz wrote:
>
> Given the many projects for which I am using CMake, I would strongly
> recommend 3.5 or higher as the minimum base. VS 2017 includes integration
> support for 3.7.2 and higher. 3.8 introduces language level standards.
>
>
>
> Mark
>
>
>
> *From:* Rick McGuire <object.r...@gmail.com> <object.r...@gmail.com>
> *Sent:* Friday, July 13, 2018 6:28 AM
> *To:* Open Object Rexx Developer Mailing List <oorexx-devel@lists.
> sourceforge.net> <oorexx-devel@lists.sourceforge.net>
> *Subject:* [Oorexx-devel] CMake minimum version and policies.
>
>
>
> I want to separate this thread out from Rony's question about the SVN
> build number.
>
>
>
> I'm thinking it is time to take a look at updating the minimum SVN version
> and the policies. Currently, we're sort stuck on CMake 2.8, while the
> latest version is 3.11. I think at a minimum, we should bump the minimum
> version to 3.0, or possibly higher.
>
>
>
> As for the CMP0010 OLD policy, this only controlled whether invalid
> variable reference syntax was a warning or an error. I'm not sure why David
> decided we needed to set this, but everything builds cleanly with the NEW
> behaviour, so I think this should just be removed. Also, if we upgrade to
> at least 3.0, we can remove the conditional setting of the CMP0042 policy,
> since that will be the default.
>
>
>
> Rick
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
