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)?
Thanks,
Boyana
--
Boyana Norris, Computer Scientist| Email: norris at mcs.anl.gov
Argonne National Laboratory
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
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
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?
Thanks!
Boyana
Matthew
The danger is that the PETSc conf/variables makefile defines its
own variables based on various variables that
are defined in PETSC_ARCH/conf/petscvariables hence the raw variable
values from running config/configure.py may not
always be what you need.
Yes, this situation has to be
Ah, ok, that explains it -- it's not in the installed version (the one
after make install). Should it be? I really would like to avoid
depending on the PETSc source directories.
Boyana
Matthew Knepley wrote:
On Thu, Jan 22, 2009 at 5:15 PM, Boyana Norris norris at mcs.anl.gov wrote:
On Jan 22, 2009, at 5:34 PM, Boyana Norris wrote:
Barry Smith wrote:
The danger is that the PETSc conf/variables makefile defines its
own variables based on various variables that
are defined in PETSC_ARCH/conf/petscvariables hence the raw
variable values from running
On Thu, Jan 22, 2009 at 5:31 PM, Boyana Norris norris at mcs.anl.gov wrote:
Ah, ok, that explains it -- it's not in the installed version (the one after
make install). Should it be? I really would like to avoid depending on the
PETSc source directories.
Technically,
1) BuildSystem is a
Matthew Knepley wrote:
On Thu, Jan 22, 2009 at 5:31 PM, Boyana Norris norris at mcs.anl.gov wrote:
Ah, ok, that explains it -- it's not in the installed version (the one after
make install). Should it be? I really would like to avoid depending on the
PETSc source directories.
On Thu, Jan 22, 2009 at 6:06 PM, Boyana Norris norris at mcs.anl.gov wrote:
Matthew Knepley wrote:
On Thu, Jan 22, 2009 at 5:31 PM, Boyana Norris norris at mcs.anl.gov wrote:
Ah, ok, that explains it -- it's not in the installed version (the one
after
make install). Should it be? I
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
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.
That would be great -- thank you!
Boyana
Matthew Knepley wrote:
I will split it into two pieces. One with a nice interface, that only
works in the
source directories OR if you install BuildSystem, and one that does nothing
but return a variable value.
Matt
On Thu, Jan 22, 2009 at 6:30
13 matches
Mail list logo
