config-options

[Andreas Grassl]

Barry Smith schrieb:
> 
>    The thing with PETSc config/configure.py options (and even more so
> with the PETSc runtime options) is that they
> are NOT centralized and they depend on each other.  We don't even know
> how many there are and all their possible
> combinations. The only access to ALL of them is via the -help option
> where the current possibilities are listed.
> When someone adds a new component to PETSc (or to its config) its
> options go with that component (not in some central file).

I understand

> 
> I guess we could add some runtime option like -defaults that would
> present all of them in a machine parsible way, it might
> be kind of messy. How important is this?

I guess, that as soon as I get more familiar with the framework I won't need it
anymore, so it is not so important.

And if troubles appear, I know where to ask ;-)

cu soon

cheers

ando

-- 
 /"\
 \ /      ASCII Ribbon
  X    against HTML email
 / \


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 315 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20090216/f2ab08de/attachment.pgp>