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
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 PM, Barry Smith wrote:
>
> Matt,
>
>I don't understand. If PETSc is
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 v
On Thu, Jan 22, 2009 at 6:18 PM, Barry Smith 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. Retre
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.
>
On Thu, Jan 22, 2009 at 6:06 PM, Boyana Norris wrote:
>
>
> Matthew Knepley wrote:
>>
>> On Thu, Jan 22, 2009 at 5:31 PM, Boyana Norris 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
Matthew Knepley wrote:
> On Thu, Jan 22, 2009 at 5:31 PM, Boyana Norris 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,
On Thu, Jan 22, 2009 at 5:31 PM, Boyana Norris 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 separate project. It ha
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 runnin
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 config/configure.py may not
> always be what you need.
Actu
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 wrote:
>
>> Thank you both -- I'd
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
On Thu, Jan 22, 2009 at 5:15 PM, Boyana Norris 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
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
Check out $PETSC_DIR/bin/configVars.py
Matt
On Thu, Jan 22, 2009 at 4:38 PM, Satish Balay 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
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 th
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
17 matches
Mail list logo
