BOINC applications, and the BOINC core client, are native-mode programs, so different versions are required for each platform (a 'platform' is the combination of an operating system and a processor type: e.g., Linux/IntelX86).

BOINC-based projects compile program versions for common platforms (Windows/Intel, Linux/Intel, Mac OS/X. etc.), and place them on its servers. A participant downloads the core client for his platform (assuming that platform is supported by the project). When the core client requests work from the project's scheduling server, the client tells the server its platform, and the server instructs it to download the appropriate executables.

This addresses the needs of most BOINC participants, but it's inadequate if:

To handle these cases, BOINC lets you make or obtain the client software yourself rather than downloading it.

First, get the BOINC client software for your computer. You can do this in either of two ways:

Second, get the project's application for your computer. Again, you can either compile it yourself or download the executable from a third party. The details vary between projects, and not all projects make their source code available. As an example, instructions for SETI@home are here.

Finally:

This model is possible only with projects that make their application source code available.

You may want to check out the following email lists (e.g. the port may already exist):

"; page_tail(); ?>