This reminds me that PETSc's build system is tied to PETSC_ARCH, thus
does not support a read-only source tree.  To do this, we would have to
make tests and Fortran stubs go into the build directory (we want that
already) and to lessen our dependence on PETSC_ARCH.  I think we should
be able to make it possible to run /path/to/petsc/configure with no
special arguments and have it set up a normal out-of-source build that
would be independent of PETSC_DIR and PETSC_ARCH.  If instead, you run
configure from PETSC_DIR, it would continue to use PETSC_ARCH as the
build directory.  (To make these otherwise uniform, PETSC_ARCH would
probably become just a hint to run make from the appropriate directory.)

Any reason we should not do this once the testing and Fortran stuff
works that way?

--- Begin Message ---
> I think I can add support for running configure out-of-directory pretty
> easily. However, before I do so, could you spell out exactly the capability
> from the build system you would like to see? For example, you mentioned
> wanting to run configure from ../../ but do you also want to run make from
> that directory as well?

Yes, of course.  I want to be able to do the following, as I can with
well-designed autotools build systems.  I am not suggesting the BLIS
build system isn't well-designed, just that it doesn't follow the
standard model that the GNU autotools community appears to advocate.

mkdir $BUILD_DIR && cd $BUILD_DIR && $BLIS_ROOT/configure
$BLIS_CONFIGURE_OPTIONS && make -j9000 && make check && make install

where 9000 is a joke (32 is more reasonable) and "make check" runs all
of the BLIS-only tests required to verify the _correctness_ of the
library.  I do not expect for "make check" to run any performance
tests or comparisons with optional third-party implementations.

Best,

Jeff

-- 
Jeff Hammond
[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"blis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/blis-devel.
For more options, visit https://groups.google.com/groups/opt_out.

--- End Message ---

Attachment: pgpeRPIw5BzYb.pgp
Description: PGP signature

Reply via email to