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 two options
1) To use mercurial - install the software from http://www.selenic.com/mercurial/wiki/index.cgi/Download [follow instructions provided]. We recommend using mercurial-0.9.3 version or newer [avoid versions older than 0.9.0]. Obtain petsc-dev with the following:
For additional help use
Compiling and
using the development copy (petsc-dev): The documentation tools (except for pdflatex) are automatically downloaded and installed by config/configure.py. However, as a failsafe, we provide them here as well. The following additional tools are required to build the PETSc documentation:
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 |
|
|