----- Mail original ----- > De: "Matthew Knepley" <[email protected]> > À: "Franck Houssen" <[email protected]> > Cc: "For users of the development version of PETSc" <[email protected]> > Envoyé: Dimanche 5 Novembre 2017 15:09:30 > Objet: Re: [petsc-dev] CMake: make, install, find_package ?
> On Sun, Nov 5, 2017 at 8:57 AM, Franck Houssen < [email protected] > > 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) > > We supported this a few years ago, but the obscene brokeness of CMake makes > this impossible, so it is no longer supported. Obscene brokeness ?! What do you mean !? Reminds me Travis-CI when I struggled to upgrade from ubuntu-12, and, had to rebuild everything during 45 mins out of the 49 mins slot available !... :D I believe this is a shame (as lots of people use cmake)... But I understand 100% the obscene part of the "dark side" ! (I escaped the Travis-CI "death star") I got that to work in 30-45 minutes (with find_package support): looks nice and stable... Personal opinion: either you decide to have a fresh look at this (things may be better now), or, you should unplug the generation of CMakeLists.txt (misleading). Franck > Thanks, > Matt > > 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 ?). > > -- > What most experimenters take for granted before they begin their experiments > is infinitely more interesting than any results to which their experiments > lead. > -- Norbert Wiener > https://www.cse.buffalo.edu/~knepley/
