On Mon, Aug 23, 2010 at 10:09 PM, Jed Brown <jed at 59a2.org> wrote: > On Mon, 23 Aug 2010 16:58:57 -0500 (CDT), Satish Balay <balay at mcs.anl.gov> > wrote: > > config/install.py is an exaple of stand alone script requiring > > PETSC_DIR/PETSC_ARCH - it also relies on being invoked in PETSC_DIR > > Do you suggest copying it's first 25 lines into all new scripts? > > > Part of the issue with PETSC_DIR/PETSC_ARCH is: they are primarily > > needed by 'makefiles' [for both building and using PETSc]. All other > > build tools - hopefully don't need them - or can autodetect as needed. > > FWIW, the CMake build doesn't use them anywhere. I just don't like > copying the autodetection all over the place. The trouble is that even > after wrapping up the autodetection, we still have to find it.
I guess it comes down to what horrifies you more: a) Changing the Python installation (I hate this) b) Having 25 lines of boilerplate in every toplevel script c) Requiring that you run it in a known place (Jed hates this) Matt > > Jed -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100823/5bc97379/attachment.html>