Changes between Version 31 and Version 32 of WrapperApp

Timestamp:

Oct 2, 2009, 10:27:07 AM (15 years ago)

Author:

atisu

Comment:

added a section at the end of page about "GenWrapper?"

WrapperApp

@@ -3 +3 @@
 A 'legacy application' is one which doesn't use the BOINC API
 (for example, because the source code is not available).
+
+== BOINC Wrapper ==
+
 Such applications can be run under BOINC using a '''wrapper''' program supplied by BOINC.
 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.
 
-== Physical file management ==
+=== Physical file management ===
 
 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.
 
-== Graphics ==
+=== Graphics ===
 
 You can include a [GraphicsApi graphics app] with a wrapper-based application.
 If you do this, pass the '''--graphics''' option to wrapper.
 
-== Example ==
+=== Example ===
 
 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.
 
+== !GenWrapper: A generic BOINC wrapper ==
+
+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!"  
+
+!GenWrapper homepage is [http://genwrapper.sourceforge.net here], documentation is [http://sourceforge.net/docman/display_doc.php?docid=182727&group_id=274859 here].
+
+
+