Scott Kruger <[email protected]> writes: > On 6/28/17 1:42 PM, Barry Smith wrote: >> >>> On Jun 28, 2017, at 2:39 PM, Scott Kruger <[email protected]> wrote: >>> >>> >>> >>> On 6/28/17 1:35 PM, Jed Brown wrote: >>>> Barry Smith <[email protected]> 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.)
signature.asc
Description: PGP signature
