Rooba
/
boinc
mirror of https://github.com/BOINC/boinc.git
1
0
Fork 0
Code Issues 1 Packages Projects Releases Wiki Activity

*** empty log message *** 

svn path=/trunk/boinc/; revision=4930
This commit is contained in:
Karl Chen 2004-12-26 00:14:51 +00:00
parent 786c1809d1
commit 15ae6fce32
2 changed files with 84 additions and 66 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

101
doc/anonymous_platform.php
View File

@ -1,38 +1,43 @@
<?php <?php
require_once("docutil.php"); require_once("docutil.php");
page_head("Compiling BOINC client software yourself"); page_head("Compiling BOINC client software yourself");
echo " ?>
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).
<p> <p>
BOINC-based projects compile program versions for common platforms BOINC applications, and the BOINC core client, are native-mode programs, so
(Windows/Intel, Linux/Intel, Mac OS/X. etc.), different versions are required for each platform (a 'platform' is the
and place them on its servers. combination of an operating system and a processor type: e.g.,
A participant downloads the core client for his platform Linux/IntelX86).
(assuming that platform is supported by the project). </p>
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.
<p> <p>
This addresses the needs of most BOINC participants, BOINC-based projects compile program versions for common platforms
but it's inadequate if: (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.
</p>
<p>
This addresses the needs of most BOINC participants, but it's inadequate if:
</p>
<ul> <ul>
<li> <li>
your computers have platforms not supported by the project; your computers have platforms not supported by the project;
</li>
<li> <li>
for security reasons, for security reasons, you want to only run executables you have compiled
you want to only run executables you have compiled yourself; yourself;
</li>
<li> <li>
you want to optimize applications for particular architectures. you want to optimize applications for particular architectures.
</li>
</ul> </ul>
<p> <p>
To handle these cases, BOINC lets you compile programs yourself To handle these cases, BOINC lets you compile programs yourself rather than
rather than downloading them from the project. downloading them from the project. Here's how it works:
Here's how it works: </p>
<ul> <ul>
<li> <li>
@ -41,16 +46,17 @@ and the project's applications, and compile them on your computer
(instructions for compiling the core client are (instructions for compiling the core client are
<a href=build_client.php>here</a>). <a href=build_client.php>here</a>).
Or download executables from a server of your choosing. Or download executables from a server of your choosing.
</li>
<li> <li>
Run the core client and attach to the project. Run the core client and attach to the project. This will create a
This will create a 'project directory' 'project directory' (whose name is the project URL) in the BOINC
(whose name is the project URL) in the BOINC directory. directory. Exit the client.
Exit the client. </li>
<li> <li>
Create a file <b>app_info.xml</b> in the project directory. Create a file <b>app_info.xml</b> in the project directory. This file
This file lists the applications you have compiled or downloaded. lists the applications you have compiled or downloaded. It has the
It has the following form: following form:
<pre>", htmlspecialchars(" <pre><![CDATA[
<app_info> <app_info>
<app> <app>
<name>setiathome</name> <name>setiathome</name>
@ -67,28 +73,37 @@ It has the following form:
</file_ref> </file_ref>
</app_version> </app_version>
</app_info> </app_info>
"), "</pre> ]]></pre>
</li>
<li> <li>
Run the core client again. Run the core client again. When it requests work from the scheduling
When it requests work from the scheduling server, server, it will report its platform as 'anonymous', and provides a list of
it will report its platform as 'anonymous', the applications it has. The server then sends whatever work is available
and provides a list of the applications it has. for those applications.
The server then sends whatever work is available for those applications. </li>
</ul> </ul>
This model is possible only with projects that make their application
source code available.
<p> <p>
You may want to check out the following email lists This model is possible only with projects that make their application source
(e.g. the port may already exist): code available.
</p>
<p>
You may want to check out the following email lists (e.g. the port may
already exist):
</p>
<ul> <ul>
<li> <li>
<a href=http://www.ssl.berkeley.edu/mailman/listinfo/boinc_opt>boinc_opt@ssl.berkeley.edu</a>: discussion of porting and optimization of BOINC applications. <a href="http://www.ssl.berkeley.edu/mailman/listinfo/boinc_opt">
boinc_opt@ssl.berkeley.edu</a>:
discussion of porting and optimization of BOINC applications.
</li>
<li> <li>
<a href=http://www.ssl.berkeley.edu/mailman/listinfo/boinc_dev>boinc_dev@ssl.berkeley.edu</a>: discussion of development and porting of BOINC software. <a href="http://www.ssl.berkeley.edu/mailman/listinfo/boinc_dev">
boinc_dev@ssl.berkeley.edu</a>: discussion of development and porting of
BOINC software.
</li>
</ul> </ul>
<p>
"; <?php
page_tail(); page_tail();
?> ?>

17
doc/docutil.php
View File

@ -6,10 +6,10 @@ function last_mod() {
function page_head($title) { function page_head($title) {
$d = last_mod(); $d = last_mod();
echo " echo "<html>
<head> <head>
<link rel='stylesheet' type='text/css' href=white.css> <link rel='stylesheet' type='text/css' href="white.css"/>
<link rel='shortcut icon' href='iconsmall.ico'> <link rel='shortcut icon' href='iconsmall.ico'/>
<title>$title</title> <title>$title</title>
</head> </head>
<body bgcolor=ffffff> <body bgcolor=ffffff>
@ -27,11 +27,14 @@ function page_head($title) {
function page_tail() { function page_tail() {
echo " echo "
<hr size=0 noshade> <hr size="0" noshade/>
<center> <p align="center">
<a href=/>Return to BOINC main page</a> <a href="/">Return to BOINC main page</a>
<br><br> <br/><br/>
Copyright &copy; 2004 University of California Copyright &copy; 2004 University of California
</p>
</body>
</html>
"; ";
} }