changes to PETSc-dev bmake system and library locations
Satish Balay
balay at mcs.anl.gov
Mon Jun 11 10:29:47 CDT 2007
On Mon, 11 Jun 2007, Lisandro Dalcin wrote:
> On 6/11/07, Satish Balay <balay at mcs.anl.gov> wrote:
> > There is nothing sepcial about having all installs inside a single
> > PETSC_DIR. in the prefix model - the user specifies prefix just
> > like any other package. For eg:
> >
> > --prefix=/usr/local --download-mpich
> >
> > This should install both the packages [PETSc & MPI] in
> > /usr/local/[bin,include,lib]
> >
>
> I see the benefits now, I will try to update my build system for
> petsc4py and see what happens...
>
> Can you please tell me what would be now the correct way to
> differentiate a 'build' mode and an 'install' mode? Just using
> directory structure?
If its based on PETSC_ARCH/PETSC_DIR from makefiles, things should
still work - [as PETSC_ARCH will be ignored by makefiles in the
prefix-install version]
Not sure what can be done or other 'automatic' detection
systems. Perhaps Barry has ideas on this.
Satish
More information about the petsc-dev
mailing list