Re: [Paraview] Required CMake version 3.5

On Fri, Jun 24, 2016 at 09:28:29 -0400, Jim wrote: > Can you let me know how it goes? I just pulled the latest versions of > Paraview & cmake and want to build under VS2015. I'm going to work on it > over the weekend. If you're doing the same, I could use any > configuration tricks you

Re: [Paraview] Required CMake version 3.5

On Fri, Jun 24, 2016 at 15:50:45 +0200, Christoph Grüninger wrote: > I don't think it is a good idea to ask for the latest version. Only > developers like us have > a current version of CMake installed. From already released distributions > nobody > provides CMake 3.5. My thought here is that

Re: [Paraview] Required CMake version 3.5

Hi Ben, I don't think it is a good idea to ask for the latest version. Only developers like us have a current version of CMake installed. From already released distributions nobody provides CMake 3.5. > Though I question the distro update policies surrounding where ParaView > is aggressively

Re: [Paraview] Required CMake version 3.5

On 06/24/2016 09:23 AM, Ben Boeckel wrote: On Fri, Jun 24, 2016 at 00:25:00 +0200, Cory Quammen wrote: @Ben, I assume all the dashboard machines are running CMake 3.5. Do you think we should downgrade one to CMake 3.3? I was actually going to upgrade them to 3.6's rc today to test it out.

Re: [Paraview] Required CMake version 3.5

On Fri, Jun 24, 2016 at 00:25:00 +0200, Cory Quammen wrote: > @Utkarsh, any foreseeable problems reducing the CMake required version to 3.3? I think we'll want 3.5 in the (hopefully) near future, so if distributions don't have a new enough CMake, they can patch it down to 3.3 in the meantime. A

Re: [Paraview] Required CMake version 3.5

On Thu, Jun 23, 2016 at 4:20 PM, Christoph Grüninger wrote: > Hi Ben, > >> I think the easiest way to check this would be to set the minimum to 3.3 >> and run against 3.5 to see if any POLICY warnings are triggered for the >> way openSUSE builds ParaView. If they are, the old

Re: [Paraview] Required CMake version 3.5

Hi Ben, > I think the easiest way to check this would be to set the minimum to 3.3 > and run against 3.5 to see if any POLICY warnings are triggered for the > way openSUSE builds ParaView. If they are, the old version is probably > silently doing something wrong. I just did exactly that, no

Re: [Paraview] Required CMake version 3.5

On Wed, Jun 22, 2016 at 05:21:33 +0200, Christoph Grüninger wrote: > thanks for link to the developer mailing list discussion. I think CMake 3.3 > is better then > 3.5, because at least the last Leap 42.1 release provides that. > I patched ParaView to require CMake 3.0 and it builds fine. I will

Re: [Paraview] Required CMake version 3.5

Hi Christoph, Thanks for the information, and again, thanks for your hard work packaging ParaView. Best regards, Cory On Wed, Jun 22, 2016 at 5:21 AM, Christoph Grüninger wrote: > Hi Cory, > thanks for link to the developer mailing list discussion. I think CMake 3.3 > is

Re: [Paraview] Required CMake version 3.5

Hi Cory, thanks for link to the developer mailing list discussion. I think CMake 3.3 is better then 3.5, because at least the last Leap 42.1 release provides that. I patched ParaView to require CMake 3.0 and it builds fine. I will package ParaView 5.1 that way and hope you reduce the requirement

Re: [Paraview] Required CMake version 3.5

Hi Christoph, Thank you for working on packaging ParaView for openSUSE! Please see this discussion in the paraview-developers mailing list archive that gives reasons for updating the required version of CMake to 3.5: http://public.kitware.com/pipermail/paraview-developers/2016-April/004229.html

[Paraview] Required CMake version 3.5

Dear Paraview developers, congratulations to the 5.1 release and thanks for your hard work! I currently try to package it for openSuse and I stumbled upon the required CMake version. What's the reason for this harsh requirement? Wouldn't be 3.0 or similar be sufficient? Currently all stable