No, No, Barry... Sorry, I was not clear enough. I was thinking in having
* In an 'install' directory prefix/bin (generated executables) prefix/include (all headers) [ Perhaps prefix/include/petsc? ] prefix/lib ( all petsc *.a and *.so libs) prefix/lib/petsc (all configuration, common and arch-specific) So if 'prefix' is '/usr' you do not generate a non standard '/usr/conf' directory. * In an 'build' directory $PETSC_DIR/bin $PETSC_DIR/include (common headers) $PETSC_DIR/conf (common config) $PETSC_DIR/$PETSC_ARCH/bin (generated executables) $PETSC_DIR/$PETSC_ARCH/include (arch-specific headers) $PETSC_DIR/$PETSC_ARCH/lib (*.a and *.so libs) $PETSC_DIR/$PETSC_ARCH/lib/petsc (arch-specific config) I think this approach retains some degree of symmetry between 'prefix' and $PETSC_DIR, and uses a more standard layout in 'prefix' What do you think? On 6/12/07, Barry Smith <bsmith at mcs.anl.gov> wrote: > > Ok, so far we have > > prefix/conf > prefix/lib/conf (or petscconf or petsc) > prefix/etc/conf (or petscconf or petsc) > prefix/share/conf (or petscconf or petsc > -- Lisandro Dalc?n --------------- Centro Internacional de M?todos Computacionales en Ingenier?a (CIMEC) Instituto de Desarrollo Tecnol?gico para la Industria Qu?mica (INTEC) Consejo Nacional de Investigaciones Cient?ficas y T?cnicas (CONICET) PTLC - G?emes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594