BTW: we don't use Autotools either. [our configure tool is homegrown] Satish
On Tue, 11 Apr 2017, Satish Balay wrote: > We never had a cmake build infrastructure.. It was always configure && make. > > However - earlier on - we did have a mode of using cmake to generate > gnumakefiles [currently depricated - it might still work] - but we've > moved on to using native gnumakefiles - so don't need cmake to > generate them anymore. > > To use the cmake generated makefiles - you would do: > > ./configure && make all-cmake > > Satish > > On Tue, 11 Apr 2017, Joachim Wuttke wrote: > > > The current source archive petsc-3.7.5.tar.gz > > comes with files > > - configure for Autotools based installation > > - CMakeLists.txt for CMake based installation > > > > However, the installation web page > > https://www.mcs.anl.gov/petsc/documentation/installation.html > > only mentions "./configure". > > > > So what is the status of support for CMake based installation? > > > > The following attempt failed: > > cd petsc-3.7.5 [the unpacked source archive] > > mkdir build > > cd build > > cmake .. > > Result: > > [...] > > CMake Error at CMakeLists.txt:4 (include): > > include could not find load file: > > /lib/petsc/conf/PETScBuildInternal.cmake > > -- Configuring incomplete, errors occurred! > > > > In-place build (which of course is disadvised) > > results in the same error. > > > > > > > >
