config-options

[Barry Smith]

    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 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?

   Barry




On Feb 16, 2009, at 4:20 PM, Andreas Grassl wrote:

> Satish Balay schrieb:
>> On Mon, 16 Feb 2009, Andreas Grassl wrote:
>>
>>> Satish Balay schrieb:
>>>> On Mon, 16 Feb 2009, Andreas Grassl wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I played around with some configure options and adapted the python
>>>>> scripts from $PETSC_DIR/config/examples, but I didn't find an  
>>>>> option to
>>>>> save the current standard options to such a script-file.
>>>> Not sure I understand the question.
>>>>
>>>> When you run configure with any set of options - and the run is
>>>> successful - you get a $PETSC_ARCH/conf/reconfigure-$PETSC_ARCH.py
>>>> file - with all these options listed in it.
>>> Ok, I start from a script like this and wanted to have the default  
>>> options,
>>> which were not set explicitly to appear in a script as well.
>>
>> Why?
>
> To have an overview of the settings and to get the full control over  
> the
> default-options, but maybe I'm thinking too paranoid and I don't  
> have to change
> any default-options.
>
> cheers
>
> ando
>
>
> -- 
> /"\
> \ /      ASCII Ribbon
>  X    against HTML email
> / \
>
>