On 3/19/19 11:57 AM, Rolf Eike Beer wrote:
> It has nothing to do with either the policies or the order of
> cmake_minimum_required() and project().
Okay. My order comment was a side note and should be corrected
either way.
> If I require version 3.0 it works, with 3.1 it fails.
See this code
Am Montag, 18. März 2019, 14:45:15 CET schrieb Brad King:
> On 3/15/19 6:10 PM, Rolf Eike Beer wrote:
> > I suspected it was a policy thing, so I tried this:
> >
> > foreach(_p RANGE 21 54)
> >
> >cmake_policy(SET CMP00${_p} OLD)
> >
> > endforeach()
>
> Only policies 51-54 were added b
Am 2019-03-18 14:45, schrieb Brad King:
On 3/15/19 6:10 PM, Rolf Eike Beer wrote:
I suspected it was a policy thing, so I tried this:
foreach(_p RANGE 21 54)
cmake_policy(SET CMP00${_p} OLD)
endforeach()
Only policies 51-54 were added between 3.0 and 3.1.
The starting point was 2.8.1
On 3/15/19 6:10 PM, Rolf Eike Beer wrote:
> I suspected it was a policy thing, so I tried this:
>
> foreach(_p RANGE 21 54)
>cmake_policy(SET CMP00${_p} OLD)
> endforeach()
Only policies 51-54 were added between 3.0 and 3.1. I suggest
testing with
cmake_minimum_required(VERSION 3.0)
> I'm trying to figure out what's actually going wrong here. At this stage in
> the log you have have already built the Subsurface installer and
> smtk_import... so what is it trying to build there?
It's running packaging/windows/smtk2ssrf-mxe-build.sh to build smtk-import/
CMakeLists.txt.
Eike
On 2019-03-15 23:10+0100 Rolf Eike Beer wrote:
Out of boredom I'm hacking a bit around in the build system of Subsurface
(https://github.com/Subsurface-divelog/subsurface). One of the things I'm
looking to is requiring a newer CMake version. And now something strange
happens:
The original code:
Out of boredom I'm hacking a bit around in the build system of Subsurface
(https://github.com/Subsurface-divelog/subsurface). One of the things I'm
looking to is requiring a newer CMake version. And now something strange
happens:
The original code:
cmake_minimum_required(VERSION 2.8.11)
This s