On Tue, Oct 13, 2015 at 11:26 AM, Arne Morten Kvarving < [email protected]> wrote:
> Yes that is the file. Cmake is beautiful for configuration, python is a > mess - all is in the eye of the beholder. I have my answer. I will patch as > long as the file exists and deal with a > No, some things are actually better than other things. This is why its engineering and not art appreciation. Matt > better way when I have to. The fact that the file is named, and looks > like, a cmake config mode file had me confused. > > -------- Opprinnelig melding -------- > Fra: Jed Brown <[email protected]> > Dato: 13.10.2015 18.15 (GMT+01:00) > Til: Satish Balay <[email protected]>, Arne Morten Kvarving < > [email protected]> > Ko: petsc-users <[email protected]> > Emne: Re: [petsc-users] petsc cmake config - BUILD_SHARED_LIBS > > Satish Balay <[email protected]> writes: > > > As mentioned - PETScConfig.cmake is primarily for building PETSc - and > > not equivalent to .pc file > > def dumpCMakeConfig(self): > ''' > Writes configuration-specific values to > ${PETSC_ARCH}/lib/petsc/conf/PETScConfig.cmake. > This file is private to PETSc and should not be included by third > parties > (a suitable file can be produced later by CMake, but this is not it). > ''' > > Arne, is this the file you are talking about? It is part of the legacy > cmake build and is used to hold the various ARCH-specific variables when > building PETSc. (Note that this build does not use CMake for configure > since CMake is disgusting for that purpose and also because we needed to > ensure that it makes all the same decisions as our configure.) It's not > for users and should not be installed. > > If you want a pkgconfig file, just use PETSc.pc. Or use FindPETSc.cmake. > -- 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
