Changes between Version 35 and Version 36 of WrapperApp
- Timestamp:
- Sep 28, 2010, 3:38:56 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WrapperApp
v35 v36 1 [[PageOutline]] 2 1 3 = The BOINC Wrapper = 2 4 … … 9 11 [[Image(http://boinc.berkeley.edu/wrapper.png)]] 10 12 11 The '''wrapper''' program is in [ExampleApps boinc/samples]. 12 It reads a file with [BoincFiles logical name] 'job.xml'. 13 The source code of wrapper is in [ExampleApps boinc/samples]. 14 You can get pre-compiled versions here: 15 16 * [http://boinc.berkeley.edu/dl/wrapper_windows_intelx86_22420.zip Win32] 17 * [http://boinc.berkeley.edu/dl/wrapper_windows_x86_64_22420.zip Win64] 18 * [http://boinc.berkeley.edu/dl/wrapper_i686-apple-darwin_22411 Mac/Intel] 19 * [http://boinc.berkeley.edu/dl/wrapper_powerpc-apple-darwin_22411 Mac/PPC] 20 21 == The job description file == 22 23 The wrapper reads a file with [BoincFiles logical name] 'job.xml'. 13 24 This file has the format: 14 25 … … 59 70 * If you run '''wrapper''' in standalone mode (while debugging), you must provide input files with the proper logical, not physical, names. 60 71 61 == = Physical file management ===72 == Physical file management == 62 73 63 74 You can use the wrapper together with [PhysicalFileManagement physical file management], … … 72 83 * In task command lines, "$PROJECT_DIR" is replaced with the project directory. 73 84 74 == = Graphics ===85 == Graphics == 75 86 76 87 You can include a [GraphicsApi graphics app] with a wrapper-based application. 77 88 If you do this, pass the '''--graphics''' option to wrapper. 78 89 79 == = Example ===90 == Example == 80 91 81 92 Here's an example that shows how to use the legacy application mechanism. … … 179 190 Then the BOINC core client copies slot/out to project/worker_nodelete_1. 180 191 181 == !GenWrapper: A generic BOINC wrapper == 182 183 When the functionality of the BOINC Wrapper is not enough, there is a generic solution which uses POSIX-like shell scripting, instead of the XML config file, for describing jobs: You can have complex control flows (loops, branches, etc), but remember "with great power must also come -- great responsibility!" 192 == !GenWrapper: A more general BOINC wrapper == 193 194 When the functionality of the BOINC Wrapper is not enough, 195 there is a generic solution which uses POSIX-like shell scripting, 196 instead of the XML config file, for describing jobs: 197 You can have complex control flows (loops, branches, etc), 198 but remember "with great power must also come -- great responsibility!" 184 199 185 200 !GenWrapper homepage is [http://genwrapper.sourceforge.net here], documentation is [http://sourceforge.net/apps/trac/genwrapper/wiki/manual here].