script to query PETSc makefile variables?

[Barry Smith]

   Matt,

     I don't understand. If PETSc is --prefix installed then  
configVars.py will not work?
So what good is it's nice help system if it don't work? Either

1) configVars.py should not be recommend as a way to get PETSc values or
2) configVars.py should be fixed so that it can get PETSc values by
     a) either removing its dependencies on things that are not there  
when someone
          wants to use it (that is its dependency on script)
     b) anything that configVars.py needs to work must be --prefix  
installed when PETSc
          is installed (I don't like the idea of needing the entire  
BuildSystem shoved in when
          PETSc is --prefix installed, this is why I suggested a).  
Maybe only script stuff needs
          to be --prefix installed with PETSc).


    Barry

On Jan 22, 2009, at 6:20 PM, Matthew Knepley wrote:

> On Thu, Jan 22, 2009 at 6:18 PM, Barry Smith <bsmith at mcs.anl.gov>  
> wrote:
>>
>> On Jan 22, 2009, at 6:17 PM, Matthew Knepley wrote:
>>
>>>>
>>>
>>> I meant something slightly different. I mean that the 'script'  
>>> module
>>> is really doing very
>>> little work in this example. It is only processing command line
>>> options. Retreiving the
>>> variables will work with only standard Python.
>>>
>>  So take out the dependency.
>
> I like it for this example. It allows a nice help system and will
> always work since this
> code is in PETSc. If you want to take the code out, then its your
> responsibility to
> take out 'script' as well.
>
>  Matt
>
>>  Barry
>>
>>> Matt
>>>
>>>> Boyana
>>>>
>>>>> Matt
>>>>>
>>>>>
>>>>>>
>>>>>> Boyana
>>>>>>
>>>>>> Matthew Knepley wrote:
>>>>>>
>>>>>>>
>>>>>>> On Thu, Jan 22, 2009 at 5:15 PM, Boyana Norris <norris at mcs.anl.gov 
>>>>>>> >
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Thank you both -- I'd prefer to use configVars.py, but it  
>>>>>>>> seems to
>>>>>>>> depend
>>>>>>>> on
>>>>>>>> the script module, which is not standard in at least Python  
>>>>>>>> 2.5.
>>>>>>>> Googling
>>>>>>>> for "python script module" is a joke, as you can imagine. Is  
>>>>>>>> this a
>>>>>>>> PETSc
>>>>>>>> thing or a general module I can get somewhere?
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> That module is in PETSc,
>>>>>>>
>>>>>>> $PETSC_DIR/config/BuildSystem
>>>>>>>
>>>>>>> Matt
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>> Boyana
>>>>>>>>
>>>>>>>> Matthew Knepley wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Check out $PETSC_DIR/bin/configVars.py
>>>>>>>>>
>>>>>>>>> Matt
>>>>>>>>>
>>>>>>>>> On Thu, Jan 22, 2009 at 4:38 PM, Satish Balay <balay at mcs.anl.gov 
>>>>>>>>> >
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, 22 Jan 2009, Boyana Norris wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Is there a script that can be used to query the values of  
>>>>>>>>>>> various
>>>>>>>>>>> variables
>>>>>>>>>>> defined in petscvariables makefile snippets (similar to  
>>>>>>>>>>> lots of
>>>>>>>>>>> linux
>>>>>>>>>>> tools'
>>>>>>>>>>> pkg-config scripts)?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [don't have canned code for this but] I've previously  
>>>>>>>>>> recommended
>>>>>>>>>> doing the following in the packages configure.. [facets now  
>>>>>>>>>> has
>>>>>>>>>> this
>>>>>>>>>> in their configure to detect petsc]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> - petsc_arch and petsc_dir are inputs to configure
>>>>>>>>>> - Create a dummy makefile on the fly
>>>>>>>>>> - run this makefile to echo relavent stuff..
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> For eg:
>>>>>>>>>> asterix:/home/balay/download-pine>cat configpetsc.sh
>>>>>>>>>> #!/bin/sh
>>>>>>>>>>
>>>>>>>>>> PETSC_ARCH=asterix64
>>>>>>>>>> PETSC_DIR=/home/balay/spetsc
>>>>>>>>>>
>>>>>>>>>> cat <<EOF > petscmake
>>>>>>>>>> PETSC_ARCH = ${PETSC_ARCH}
>>>>>>>>>> PETSC_DIR  = ${PETSC_DIR}
>>>>>>>>>> include ${PETSC_DIR}/conf/base
>>>>>>>>>> EOF
>>>>>>>>>>
>>>>>>>>>> PETSC_INC=`make -f petscmake getincludedirs`
>>>>>>>>>> PETSC_LIB=`make -f petscmake getlinklibs`
>>>>>>>>>>
>>>>>>>>>> echo '**** PETSC_INC ***'
>>>>>>>>>> echo ${PETSC_INC}
>>>>>>>>>> echo '**** PETSC_LIB ***'
>>>>>>>>>> echo ${PETSC_LIB}
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Satish
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Boyana Norris, Computer Scientist    |   Email: norris at mcs.anl.gov
>>>>>>>> Argonne National Laboratory          |   Phone: +1 (630) 252  
>>>>>>>> 7908
>>>>>>>> http://www.mcs.anl.gov/~norris/      |   Fax:   +1 (630) 252  
>>>>>>>> 5986
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Boyana Norris, Computer Scientist    |   Email:  
>>>>>> norris at mcs.anl.gov
>>>>>> Argonne National Laboratory          |   Phone: +1 (630) 252 7908
>>>>>> http://www.mcs.anl.gov/~norris/      |   Fax:   +1 (630) 252 5986
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Boyana Norris, Computer Scientist    |   Email: norris at mcs.anl.gov
>>>> Argonne National Laboratory          |   Phone: +1 (630) 252 7908
>>>> http://www.mcs.anl.gov/~norris/      |   Fax:   +1 (630) 252 5986
>>>>
>>>
>>>
>>>
>>> --
>>> 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
>>
>>
>
>
>
> -- 
> 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