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

> On Nov 5, 2017, at 8:01 AM, Jed Brown 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.

Re: [petsc-dev] broken nightlybuilds (next vs next-tmp)

On Sun, 5 Nov 2017, Satish Balay wrote: > On Sat, 4 Nov 2017, Satish Balay wrote: > > > $ git fetch -p && comm -12 <(git branch -r --merged origin/next-tmp | sort) > > <(git branch -r --no-merged origin/master | sort) > > origin/barry/fix-matsettype-forsubclasses > >

Re: [petsc-dev] DMPlexCreateMedFromFile broken

On Thu, Nov 2, 2017 at 12:08 PM, Vaclav Hapla wrote: > It seems that DMPlexCreateMedFromFile leaves out some mesh elements. I > found it out when investigating why ParMetis redistribution crashes. > > I attach the datafile >

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

OK, guys, let's summarize: - I just say that generating a CMakeLists.txt (that can't be used) IS misleading for any users ! :D - You don't want to deal with CMake: OK, I am fine with that, no problem (I can understand that). - Now I know (!...), I'll stick to pkg-config... Because now I know !

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

On Sun, 5 Nov 2017, Jed Brown wrote: > Franck Houssen writes: > > > Here is a bundle you can pull for you to have a look (franck/cmake branch - > > push KO to the bitbucket as I don't know which loggin/password to use): > > take it or leave it ! :D > > > > On debian,

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

Franck Houssen writes: > Here is a bundle you can pull for you to have a look (franck/cmake branch - > push KO to the bitbucket as I don't know which loggin/password to use): take > it or leave it ! :D > > On debian, I have a "real" cmake build (not the configure

Re: [petsc-dev] broken nightlybuilds (next vs next-tmp)

On Sat, 4 Nov 2017, Satish Balay wrote: > $ git fetch -p && comm -12 <(git branch -r --merged origin/next-tmp | sort) > <(git branch -r --no-merged origin/master | sort) > origin/barry/fix-matsettype-forsubclasses > origin/jed/fix-stdout-attr-delete > origin/jed/pastix-comm >

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

Satish Balay writes: > On Sun, 5 Nov 2017, Franck Houssen wrote: > >> 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). > > Hm - configure prints at the

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

Here is a bundle you can pull for you to have a look (franck/cmake branch - push KO to the bitbucket as I don't know which loggin/password to use): take it or leave it ! :D On debian, I have a "real" cmake build (not the configure traces) in a dedicated BUILD directory (make things cleaner).

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

On Sun, Nov 5, 2017 at 9:37 AM, Franck Houssen wrote: > -- > > *De: *"Matthew Knepley" > *À: *"Franck Houssen" > *Cc: *"For users of the development version of PETSc" < > petsc-dev@mcs.anl.gov> >

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

On Sun, 5 Nov 2017, Franck Houssen wrote: > > Or are you having trouble with > > https://github.com/jedbrown/cmake-modules/blob/master/FindPETSc.cmake ? > > [and not with PETSc build?] > > At first, I was trying to understand why find_package(petsc) was not working. > So then, I looked at the

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

On Sun, 5 Nov 2017, Franck Houssen wrote: > 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). Hm - configure prints at the end:

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

- Mail original - > De: "Satish Balay" > À: "petsc-dev" > Cc: "Franck Houssen" > Envoyé: Dimanche 5 Novembre 2017 15:16:48 > Objet: Re: [petsc-dev] CMake: make, install, find_package ? > > BTW: why are prefering

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

- Mail original - > De: "Matthew Knepley" > À: "Franck Houssen" > Cc: "For users of the development version of PETSc" > Envoyé: Dimanche 5 Novembre 2017 15:09:30 > Objet: Re: [petsc-dev] CMake: make, install,

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

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.

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

On Sun, Nov 5, 2017 at 8:57 AM, 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,

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

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 ?

Re: [petsc-dev] composite vs. shell

Makes perfect sense. Thanks, Pierre > On 5 Nov 2017, at 2:52 AM, Jed Brown wrote: > > PCSetUp_Composite propagates the outer matrices to the inner PCs. > > while (next) { >ierr = PCSetDM(next->pc,dm);CHKERRQ(ierr); >ierr =