[petsc-dev] snes/ex56 target is gone

Jed Brown jed at jedbrown.org
Wed Jun 28 17:46:31 CDT 2017

Scott Kruger <kruger at txcorp.com> writes:

> On 6/28/17 2:50 PM, Jed Brown wrote:
>> 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. 
> I always thought the standard was:
>    "lib is for libraries and share is for datafiles"
> rather than
>    "lib is for platform-dependent and share is for platform independent".
> Actually, the standard itself is confusing as where
> to put platform-dependent datafiles.

What standard?

>> 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.)
> The example in Makefile.example could refer to
> either "compile examples" 

Yes, it does more than that.

> or "here is an example makefile that you can use as a starting point".

Yes, in which case it should include the stuff mentioned above to help
users extend into good Makefiles.
-------------- 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/de69b0bf/attachment.sig>

More information about the petsc-dev mailing list