Changes between Version 31 and Version 32 of WrapperApp
- Timestamp:
- 10/02/09 10:27:07 (2 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WrapperApp
v31 v32 3 3 A 'legacy application' is one which doesn't use the BOINC API 4 4 (for example, because the source code is not available). 5 6 == BOINC Wrapper == 7 5 8 Such applications can be run under BOINC using a '''wrapper''' program supplied by BOINC. 6 9 The wrapper runs legacy applications as subprocesses, 60 63 * If you run '''wrapper''' in standalone mode (while debugging), you must provide input files with the proper logical, not physical, names. 61 64 62 == Physical file management==65 === Physical file management === 63 66 64 67 You can use the wrapper together with [PhysicalFileManagement physical file management], 73 76 * In task command lines, "$PROJECT_DIR" is replaced with the project directory. 74 77 75 == Graphics==78 === Graphics === 76 79 77 80 You can include a [GraphicsApi graphics app] with a wrapper-based application. 78 81 If you do this, pass the '''--graphics''' option to wrapper. 79 82 80 == Example==83 === Example === 81 84 82 85 Here's an example that shows how to use the legacy application mechanism. 180 183 Then the BOINC core client copies slot/out to project/worker_nodelete_1. 181 184 185 == !GenWrapper: A generic BOINC wrapper == 186 187 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!" 188 189 !GenWrapper homepage is [http://genwrapper.sourceforge.net here], documentation is [http://sourceforge.net/docman/display_doc.php?docid=182727&group_id=274859 here]. 190 191 192
