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

[Satish Balay]

BTW: why are prefering all-cmake build over all-gnumake build?

Or are you having trouble with
https://github.com/jedbrown/cmake-modules/blob/master/FindPETSc.cmake ?
[and not with PETSc build?]

Satish

On Sun, 5 Nov 2017, Satish Balay wrote:

> PETSc has 3 modes of building libraries
> 
> 1. all-legacy: using legacy makefiles [which uses vanila make in recursive mode]
> 2. all-cmake: using cmake to generate gnumakefiles
> 3. all-gnumake: using gnumakefiles
> 
> Now all-gnumake build is the default/primary. with it working in all
> cases - there is no real reason for all-cmake build.
> 
> [we still use all-legacy for documentation generation and examples, and a few other cases]
> 
> So all-cmake is not tested and unsupported. But the code is still there and is not removed [or updated]
> 
> However - I just tired a simple 'all-cmake' build - and that worked. [attaching make.log]
> 
> What did not work for you? Please send relavent logs.
> 
> Satish
> 
> On Sun, 5 Nov 2017, Franck Houssen wrote:
> 
> > Hello, 
> > 
> > Does PETSc provide support for CMake ? I would say this is an on-going feature that is not yet fully working, right ? 
> > My understanding is that "./configure" generates the CMakeLists.txt. But then, when using cmake, make fails. 
> > Is this supposed to work yet ? Or is this on-going dev ? (google is misleading about that, and, not seen anything in the doc) 
> > 
> > Franck 
> > 
> > PS : I got it to work (partially - for petsc, not external packages) on my laptop (debian). I may (?) push I somebody is interested to have a look (on going dev ?). 
> > 
>