In this approach, the BOINC-based project compiles program versions for common platforms (Windows/Intel, Linux/Intel, Mac OS/X. etc.), and places them on its servers. A participant downloads the core client for his platform (assuming that it's 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 for some people:

• People who, for security reasons, want to only run executables they have compiled themselves.
• People whose computers have platforms not supported by the project.
• People who want to optimize applications for particular architectures.

The compile-it-yourself model

In this model participants compile programs themselves rather than downloading them from the project. Here's how it works:

• Download the source code for the BOINC core client and the project's applications, and compile them on your computer (instructions for compiling the core client are here). Or download executables from a server of your choosing.
• Run the core client and attach to the project. This will create a 'project directory' (whose name is the project URL) in the BOINC directory. Exit the client.
• Create a file app_info.xml in the project directory. This file lists the applications you have compiled or downloaded. It has the following form:

  ", htmlspecialchars("
  
      
          setiathome
      
      
          setiathome_2.18_windows_intelx86.exe
      
      
          setiathome
          218
          
              setiathome_2.18_windows_intelx86.exe
              
          
      
  
  "), "

• Run the core client again. When it requests work from the scheduling server, it will report its platform as 'anonymous', and provides a list of the applications it has. The server then sends whatever work is available for those applications.

"; page_tail(); ?>