On Mon, 23 Aug 2010, Jed Brown 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?
I guess thats the current recomendation. >From previous edits - Barry doesn't like these provided as command line arguments to the stand alone scripts. There is also config/builder.py - that doesn't work witout PETSC_DIR env variable. And I don't like over reliance on evn variables - when its not needed - esp for build tools. These give rise to undebuggable errors [wrong buildsytem used from a different PETSC_DIR source tree etc - or generated files are dumped into the wrong PETSc tree etc....] Also we are opposed to CC CFLAGS etc in env variables. So in that line of things PETSC_DIR/PETSC_ARCH reliance should also be minimised - [avoided - when not needed] Now that there are more and more standalone scripts - perhaps we need a better consistant way to handle this - but I don't know what that is.. Satish > > 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.