[petsc-dev] snes/ex56 target is gone

Jed Brown jed at jedbrown.org
Wed Jun 28 15:50:54 CDT 2017

Scott Kruger <kruger at txcorp.com> writes:

> On 6/28/17 1:42 PM, Barry Smith wrote:
>>> On Jun 28, 2017, at 2:39 PM, Scott Kruger <kruger at txcorp.com> wrote:
>>> On 6/28/17 1:35 PM, Jed Brown wrote:
>>>> Barry Smith <bsmith at mcs.anl.gov> writes:
>>>>>     Jed,
>>>>>      Aside from its name and location this is a very useful thing. Should it be in $PETSC_DIR/lib/petsc/conf/ ? since it cannot stay in $PETSC_DIR for --prefix installs?
>>>> I guess that's a reasonable location.  The file isn't platform-dependent
>>>> so it could go elsewhere.  In that location, it should acquire a line
>>>> specifying PETSC_ARCH upon install.  The only issue with the path is
>>>> that you're actually typing it on the command line, and that would be
>>>> a starter Makefile for anyone building a larger project.
>>> I would prefer share as it's not critical to the conf
>>> and is more user oriented (I think of lib/petsc/conf
>>> as internal to petsc stuff).
>>    So $PETSC_DIR/share/petsc/?
> What would be perfect for me with something like Makefile.example as
> the name.

That's fine, but the use is not limited to examples.  If we're calling
this the example makefile, we should at least add comments saying how to
build more complicated programs.  (Just listing the target dependencies
gets you much of the way.  Adding accurate dependencies is slightly more
work but we ought to recommend a clean way because lots of people make a
mess of it.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20170628/c2bf18d3/attachment.sig>

More information about the petsc-dev mailing list