Changes between Version 10 and Version 11 of MakeProject

Timestamp:

Jul 12, 2007, 11:18:27 AM (17 years ago)

Author:

ijgeneral

Comment:

--

MakeProject

@@ -67 +67 @@
 Assuming you have a legacy application (i. e., an executable not using the Boinc API), you can make it run under Boinc through the use of the wrapper application. In case you don't already have that application, you can download it, along with some other samples, doing 'svn co http://boinc.berkeley.edu/svn/trunk/boinc_samples'. 
 Let's say that your application is located at /home/ABC/ and the name of the executable is abc. Assume that the command needed to run it is:
-
+{{{
     > abc -i input.in -p parameters.in -o output.out
-
+}}}
 Now, do the following (the paths I use are those corresponding to the Debian virtual machine; adjust accordingly to your installation):
-
+{{{
     > cd /home/boincadm/boinc_samples/wrapper
-
-    > ln -s 'g++ -print-file-name=libstdc++.a'
-
+    > ln -s `g++ -print-file-name=libstdc++.a`
+}}}
 Edit the Makefile for wrapper and change the BOINC_DIR variable according to your installation (in the Debian virtual machine this would be BOINC_DIR=/home/boincadm/boinc_trunk).
-
+{{{
     > make
+}}}
 So far, you have created the wrapper executable.
-
+{{{
     > cd /home/boincadm/boinc_trunk/tools
-
     > ./make_project abc (or any other name you want to use)
-
     > su
-
     > cat /home/boincadm/projects/abc/abc.httpd.conf >> /etc/apache2/httpd.conf
-
     > apache2ctl restart
-
     > exit
-
+}}}
 Now, you have created the directory structure for your project, named abc, with some project's control files. Also, you have modified the Apache configuration to make it serve your project.
-
+{{{
     > cd /home/boincadm/projects/abc
-
     > crontab abc.cronjob
-
     > cd apps; mkdir abc; cd abc
-
     > mkdir wrapper_1.01_i686-pc-linux-gnu (this name has the format wrapper_version_architecture-operating-system)
-
     > cd wrapper_1.01_i686-pc-linux-gnu
-
     > cp /home/ABC/abc abc_1.01_i686-pc-linux-gnu (use same format as with the directory above)
-
     > cp /home/boincadm/boinc_samples/wrapper/wrapper wrapper_1.01_i686-pc-linux-gnu
-
     > vi job.xml=job_1.01.xml
-
-The contents of this file, for the abc application, are
+}}}
+The contents of this file, job.xml=job_1.01.xml, for the abc application are
 
 {{{
@@ -123 +111 @@
 </job_desc>
 }}}
-
+{{{
     > cd /home/boincadm/projects/abc/templates
-
     > vi abc_wu (this is the work-unit template)
-
+}}}
 Contents of abc_wu:
-
 {{{
 <file_info>
@@ -155 +141 @@
 }}}
 
+{{{
     > vi abc_result (this is the results template)
-
+}}}
+Contents of abc_result:
 {{{
 <file_info>
@@ -174 +162 @@
 }}}
 
+{{{
     > cd ..
-
     > vi project.xml
-
+}}}
 and change the application name in the last few lines of the file:
 
@@ -192 +180 @@
 
 Now, you have all the files in place, so let's tell Boinc to add the project to the database and to copy the files it will need to the download directory. Then, start the project's daemons:
-
+{{{
     > bin/xadd
-
     > bin/update_versions
-
     > bin/start
-
+}}}
 Put your input files (input.in and parameters.in) in /home/boincadm/projects/abc/download/. Then do:
-
-    > cp download/input.in 'bin/dir_hier_path input.in'
-
-    > cp download/parameters.in 'bin/dir_hier_path parameters.in'
-
+{{{
+    > cp download/input.in `bin/dir_hier_path input.in`
+    > cp download/parameters.in `bin/dir_hier_path parameters.in`
     > bin/create_work -appname abc -wu_name abc-nodelete01 -wu_template templates/abc_wu -result_template templates/abc_result input.in parameters.in
-
+}}}
 The last step creates a workunit. This will be sent to a client attached to this project, who will perform the required work and return the results to the upload directory. The project should be functional and accessible now to any Boinc client.