Changes between Version 6 and Version 7 of Public/User_Guide/JUBE

Timestamp:

Aug 4, 2016, 4:25:02 PM (9 years ago)

Author:

Cristina Manzano

Comment:

—

Public/User_Guide/JUBE

@@ -86 +86 @@
 The values in the set of parameters with name "systemParamter" will be initialized with the default values found in the file "MAXW-DGTD_specs.xml". This last file takes in turn some of the default values of platform.xml and overwrites them. See the file for more information.
 
+We can reference other parameters with $ like in the example $k or $jube_benchmark_home. $jube_benchmark_home is a JUBE variable with the value of the original input file location and $k is 2:
+
+{{{
+    <parameterset init_with="MAXW-DGTD_specs.xml" name="MAXW-DGTDParameter-head">
+      <parameter name="k" type="int" >2</parameter>
+    </parameterset>
+}}}
+
+So the value of the targetdir parameter will be /usr/local/deep-er/sdv-benchmarks/applications/MAXW-DGTD/executable/k2
+
 5) Step compile
 
@@ -101 +111 @@
 
 In the step compile we tell which parameters and source files to use with the tag <use></use>. The <do></do> contains a single shell command. This command will run inside of a sandbox directory environment (inside the outpath directory tree).
+
+6) Step copy_exec
+
+{{{
+    <step depend="compile" name="copy_exec">
+      <use>systemParameter</use>
+      <use>MAXW-DGTDParameter-head</use>
+      <do>mkdir -p $targetdir</do>
+      <do>cp -p compile/MAXW-DGTD/exe/gdL$k $targetdir/gdL$k-jubeID_$jube_benchmark_id</do>
+      <do>rm -f $targetdir/gdL$k; ln -s $targetdir/gdL$k-jubeID_$jube_benchmark_id $targetdir/gdL$k</do>
+    </step>
+}}}
+
+The copy_exec step depends on the compile step and will wait until it is finished for copying the executables resulting from the compilation to the $targetdir directory.