• Get the source code for both boinc and boinc_samples. Put them in the same parent directory; otherwise relative paths won't work.
• If you're working on Unix, Build the BOINC software (you only need the api/ and lib/ parts of it). On Windows, this will be done automatically as part of building the application.

• upper_case: a full-featured example BOINC application. The application does things (like checkpointing and graphics) that can be tricky or confusing. You can use it as a template for your own BOINC application; just rip out the computation part (which is trivial) and replace it with your code.

  The graphics show a bouncing 3D ball. If you put files Helvetica.txf and logo.jpg in the directory where it runs, you'll also see an image and some nice-looking text (thanks to Tolu Aina for the latter).

• wrapper: used to support legacy applications.
• worker: a representative 'legacy' application (i.e. it doesn't use the BOINC API or runtime library). Used for testing wrapper.
• sleeper: test application for non-CPU-intensive projects (used for testing the BOINC core client).

The boinc_samples tree includes project files for the following platforms:

• Windows: includes project files for Microsoft Visual Studio 2003 and 2005. Also includes a project file samples.dev for Dev-C++, a free development environment for Windows (this project file doesn't work yet). These are in the win_build/ directory.
• Mac OS X: includes an Xcode project file for upper_case, mac_build/UpperCase.xcodeproj
• Linux: includes a Makefile for building on Linux. For upper_case, this produces a separate .so containing the graphics part. The Makefile links some libraries statically (stdc++, glut etc.) so that the app will run on machines where these are old or missing. It also uses a technique where the main program exports its symbols to the graphics .so, which eliminates lots of the problems we had in Einstein@home.

"; page_tail(); ?>