[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source
Matthew Knepley
knepley at gmail.com
Tue May 4 11:37:14 CDT 2010
On Tue, May 4, 2010 at 11:26 AM, Jed Brown <jed at 59a2.org> wrote:
> On Tue, 4 May 2010 11:21:25 -0500, Matthew Knepley <knepley at gmail.com>
> wrote:
> > Each configure test is a Python module. The modules are organized in a
> > DB. You can request a module using its full name. When you get the
> > module reference you can query all of its attributes. For instance,
> >
> > config.PETSc.utilities.scalarTypes has attribute "scalartype" which
> > can be "real" or "complex"
> >
> > Same for 3rd party packages, which all inherit from
> > config.package.Package.
>
> I wasn't asking how these values were set. Looking at the source, I see
> that checkDir() parses the makefiles and processes lines starting with
> #requires.
I see. Yes, it currently uses the makefile organization. This is the kind of
metadata
that Barry would like in a DB rather than in makefiles.
Matt
>
> Jed
--
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100504/e28a0af2/attachment.html>
More information about the petsc-dev
mailing list