[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

[Matthew Knepley]

On Tue, May 4, 2010 at 11:16 AM, Jed Brown <jed at 59a2.org> wrote:

> On Tue, 4 May 2010 11:09:59 -0500, Matthew Knepley <knepley at gmail.com>
> wrote:
> > All the build metadata is in an OO database in Python. builder.py
> > extracts it in order to do the build.
>
> How does builder.py find out which optional stuff to build, the stuff
> that is in the makefiles with #requirespackage, #requiresprecision, etc?


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.

  Thanks,

     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/f2e21e5c/attachment.html>