dolfin team mailing list archive

[Matthew Knepley <knepley@xxxxxxxxxxx>]

Anders Logg <logg@xxxxxxxxx> writes:
>> > But all I need to compile against PETSc is a single text string and I get
>> > the same string every time I do 'make getincludedirs'.
>> 
>>   No, you get a different string depending on the value of
>>   PETSC_ARCH.
>
> Yes, but PETSC_ARCH is known at compile-time (of PETSc) and then the
> script could be generated. And PETSC_ARCH stays constant over time, at
> least on my machine... :-)
>
>> >>       However, we have compromised and provided a simple way to get the
>> >> flags. Does it matter whether the script is called makefile or petsc-config?
>> >> You would still need all the bmake stuff to get the right answer anyway. Right?
>> >
>> > It matters since if it were called petsc-config I wouldn't have had to
>> > ask you how to do it.
>> 
>>   make <option>   <-->    petsc-config <option>
>> 
>> and you would will need all the bmake directories.
>
> Yes, but the bmake directories would not be needed after PETSc has
> been installed and the script been generated. Or am I missing something?

  This is important. Unless you want to allow only a single PETSC_ARCH at install
time, you would need a separate petsc-config for each arch, or a single complicated
one. That is why we use make which handles this both seamlessly, and also dynamically
in that new archs are incorporated automatically as they appear, whereas the petsc-config
model would require considerable fixup, or a separate script each time.

      Matt
-- 
"Failure has a thousand explanations. Success doesn't need one" -- Sir Alec Guiness