[petsc-dev] CMake: make, install, find_package ?

Smith, Barry F. bsmith at mcs.anl.gov
Sun Nov 5 13:44:45 CST 2017

> On Nov 5, 2017, at 8:01 AM, Jed Brown <jed at jedbrown.org> wrote:
>> Sure - if you hunt arround the PETSc source tree - you will find bunch
>> of stuff.. [but that would be ignoring the primary doc].
>> Also There was some reason Jed didn't want to strip out the cmake
>> stuff. Perhaps FindPETSc.cmake uses it?
> No, FindPETSc does not use it.  And I would recommend using CMake's
> pkg-config instead of FindPETSc if you have a current version of PETSc.
> I think the reason for not stripping it entirely was that theoretically
> it could be useful for IDE integration and/or a native Windows build.
> Should probably delete it to avoid confusing someone that is grepping
> around.


     Can you do the strip or tell us exactly what directories and files to strip and what rules from the makefiles. It is time to get rid of this obscenity since you replaced it with the far better and more reliable version that uses gnumake.



> Franck, we've had a number of problems over the years with CMake
> seg-faulting and going into infinite loops in some reconfiguration
> scenarios.  Possible to work around, but we were fielding frequent
> support emails due to CMake bugs and installation problems.  The build
> got faster, more accurate, and simpler when we switched to GNU Make.
> And the support emails stopped.  You're welcome to use CMake, but we are
> not fans.

More information about the petsc-dev mailing list