PETSc |
Developers Site |
|
|
|
|
These pages are for people interested in
using the development
copy of PETSc (called petsc-dev) or contributing to the PETSc
libraries. It is intended
only
for people who are experienced with building, using and debugging
PETSc. If you cannot use makefiles, a debugger and EMACS etags then
please don't access these pages. Consider joining petsc-dev mailing-list. How to:
Browsing Source: One can browse the development repositories at the following location Obtaining the development version of PETSc: You have three options
For additional help use
2) One can obtain the current petsc-dev and BuildSystem repositories as tarballs from the mercurial server using the following URLs. http://petsc.cs.iit.edu/petsc/petsc-dev/archive/tip.tar.gz http://petsc.cs.iit.edu/petsc/BuildSystem/archive/tip.tar.gz Note1: This mode is useful - if you are on a machine where you cannot install mercurial - or if it has a firewall blocking http downloads. Note2: If using firefox to download - the tarballs will get the names petsc-dev-changesetid.tar.gz and BuildSystem-changesetid.tar.gz. However, if wget is used - both tarballs will get the name 'tip.tar.gz'. In this case rename the tarballs [to avoid the name conflict]. After both the tarballs are obtained - do the following:
3) The nightly tarball will be equivalent to the release tarball - with all the doumentation built. To use the nightly tarball snapshot, simply download http://ftp.mcs.anl.gov/pub/petsc/petsc-dev.tar.gz and extract it.
Compiling and
using the development copy (petsc-dev): The documentation tools listed below (except for pdflatex) are automatically downloaded and installed by config/configure.py.
Once pdflatex (from teTeX) is in
your PATH you can build the documentation with:
Sending patches to update the master copy of petsc-dev: One can
send us changes to PETSc [perhaps bug fixes or new feature additions]
via e-mail. One easy way to do this [if no new files get created] is:
Alternatively - one can send us patches using 'hg bundle' as described at http://www.selenic.com/mercurial/wiki/index.cgi/CommunicatingChanges Once you have developed experience with developing PETSc source code you can become an active member of our development and push changes directly to the petsc-dev repository. Send mail to petsc-maint@mcs.anl.gov to arrange it. The logs for the nightly builds at http://ftp.mcs.anl.gov/pub/petsc/nightlylogs PETSc developers can automatically log into any PETSc test directory with ${PETSC_DIR}/bin/maint/petscgoto arch-of-test-system The coverage (what lines of source code are tested in the nightly builds) can be found at http:/www.mcs.anl.gov/petsc/petsc-as/snapshots/petsc-dev/index_gcov1.html |
| |
|