BOINC is distributed via CVS, tarballs compressed with gzip, and Windows zip files.

If installing from CVS, check out the entire CVS tree.
If installing on Windows, unzip boinc.zip or boinc.tar.gz, and unzip win_build.zip inside the BOINC directory.
If installing on Mac OS X, unzip boinc.zip or boinc.tar.gz, and unstuff mac_build.sit inside the BOINC directory.

Unpacking the BOINC source code creates the following directories:

RSAEuro/: An RSA implementation (included for convenience; not covered under the BOINC public license).
api/: The BOINC API (for applications)
apps/: Some test applications.
client/: The BOINC core client.
client/win/: Core client files particular to the Windows GUI version.
db/: The database schema and interface functions.
doc/: HTML documentation files.
html_ops/: PHP files for the operational web interface.
html_user/: PHP files for the participant web interface.
lib/: Code that is shared by more than one component (core client, scheduling server, etc.).
sched/: The scheduling server, feeder, and file upload handler.
sched_fcgi/: Separate directory for compiling the server and file upload handler as Fast CGI programs.
test/: Test scripts.
tools/: Operational utility programs.

On UNIX systems, the BOINC software (both server and client) can be built by typing

  ./_autosetup  [Only needed if using CVS; not needed if using tarball]
  ./configure
  make
  make install  [Optional: installs libraries and header files useful for building apps]

in the top directory. If you want to build the Unix/Mac graphical client, you will need to install wxWidgets. Automatic tests can be run using:

  make check

A list of options to the configure script can be found by using

./configure --help

The most useful of these is

./configure --prefix=/path/to/install/headers/and/libraries/

Note that if building from CVS you should have fairly recent versions of autoconf and automake installed. These are maintained by the GNU project. "; page_tail(); ?>