Changes between Version 60 and Version 61 of WrapperApp

Timestamp:

Nov 13, 2012, 10:51:36 PM (12 years ago)

Author:

davea

Comment:

--

WrapperApp

@@ -79 +79 @@
 Notes:
  * One or more of the tasks may be [AppMultiThread multi-threaded] and/or [AppCoprocessor use GPUs]. 
- * Normally the job file is part of the application version (it's the same between workunits).  Alternatively, it can be part of the workunit (e.g. if its command line elements differ between workunits).  This requires that you use the same worker program logical names for all platforms.
- * Files opened directly by a worker program must have the <copy_file/> tag. This requires version 5.5 or higher of the BOINC core client (you can specify this limit at either the [AppVersion application] or [ProjectOptions#Clientcontrol project] level.
+ * Normally the job file is part of the application version (it's the same between workunits).
+  Alternatively, it can be part of the workunit (e.g. if its command line elements differ between workunits).
+  This requires that you use the same worker program logical names for all platforms.
+ * Files opened directly by a worker program must have the <copy_file/> tag.
+  This requires version 5.5 or higher of the BOINC core client (you can specify this limit at either the
+  [AppVersion application] or [ProjectOptions#Clientcontrol project] level.
  * Worker programs must exit with zero status; nonzero values are interpreted as errors by the wrapper.
- * If you run '''wrapper''' in standalone mode (while debugging), you must provide input files with the proper logical, not physical, names.
- * The job file may be slightly different for different platforms (i.e. app_versions) due to directory requirements (exec_dir) and environment variables (setenv) required.  You will therefore want to make and track different versions for each app_version you are supporting.
-
+ * If you run '''wrapper''' in standalone mode (while debugging),
+  you must provide input files with the proper logical, not physical, names.
+ * The job file may be slightly different for different platforms (i.e. app_versions)
+  due to directory requirements (exec_dir) and environment variables (setenv) required.
+  You will therefore want to make and track different versions for each app_version you are supporting.
 
 == Example ==
@@ -97 +103 @@
 Now
  * Download the wrapper for Win32 (see links above) to your server
-  .Assume the filename is '''wrapper_windows_intelx86_22420.exe'''.
+  .Assume the filename is '''wrapper_windows_intelx86_25825.exe'''.
  * [AppVersion Create an application] named 'worker'.
  * Create the directory hierarchy
@@ -106 +112 @@
          windows_intelx86/
 }}}
- * Put the files '''wrapper_windows_intelx86_22420.exe'''
+ * Put the files '''wrapper_windows_intelx86_25825.exe'''
   and '''worker_windows_intelx86_0.exe''' in the bottom directory.
  * In the same directory, create a file '''worker_job_1.0.xml'''
@@ -122 +128 @@
 <version>
    <file>
-      <physical_name>wrapper_windows_intelx86_22420.exe</physical_name>
+      <physical_name>wrapper_windows_intelx86_25825.exe</physical_name>
       <main_program/>
    </file>