Skip to contentSkip to conversation

new PTEST_RUN_SCRIPT_PATH

PATCH In review Ian Ray 1 participant 3 messages Sep 18, 2015 – Oct 6, 2015

lore
Share & tools
lore

Ian Ray

author
#0 lore raw

cover new PTEST_RUN_SCRIPT_PATH

New PTEST_RUN_SCRIPT_PATH allows recipes to override the default location of the run-ptest script.

Ian Ray (1):
ref-manual, dev-manual: Updates to support PTEST_RUN_SCRIPT_PATH.

 documentation/dev-manual/dev-manual-common-tasks.xml |  5 ++++-
 documentation/ref-manual/ref-variables.xml           | 15 +++++++++++++++
 2 files changed, 19 insertions(+), 1 deletion(-)
Signature · 1 line
1.8.3.1
author
#1 lore raw

PATCH 1/1 ref-manual, dev-manual: Updates to support PTEST_RUN_SCRIPT_PATH.

In the ref-manual, I added a new variable description for the PTEST_RUN_SCRIPT_PATH variable.

In the dev-manual, I added a note to the "Getting Your Package Ready" section to mention that PTEST_RUN_SCRIPT_PATH can be used to locate the run-ptest script.

---
 documentation/dev-manual/dev-manual-common-tasks.xml |  5 ++++-
 documentation/ref-manual/ref-variables.xml           | 15 +++++++++++++++
 2 files changed, 19 insertions(+), 1 deletion(-)
documentation/dev-manual/dev-manual-common-tasks.xml +4 -1
index 7a28176..cd5bf51 100644
@@ -7357,7 +7357,10 @@
                             This script starts your test.
                             Locate the script where you will refer to it
                             using
-                            <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>.
+                            <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink> or
+                            <ulink url='&YOCTO_DOCS_REF_URL;#var-PTEST_RUN_SCRIPT_PATH'><filename>PTEST_RUN_SCRIPT_PATH</filename></ulink>
+                            if the ptest-run script is included with the recipe sources and unpacked to
+                            <ulink url='&YOCTO_DOCS_REF_URL;#var-S'><filename>S</filename></ulink>.
                             Here is an example that starts a test for
                             <filename>dbus</filename>:
                             <literallayout class='monospaced'>
documentation/ref-manual/ref-variables.xml +15 -0
index ecac2b6..7cc30c1 100644
@@ -9188,6 +9188,21 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
             </glossdef>
         </glossentry>
 
+        <glossentry id='var-PTEST_RUN_SCRIPT_PATH'><glossterm>PTEST_RUN_SCRIPT_PATH</glossterm>
+            <info>
+                PTEST_RUN_SCRIPT_PATH[doc] = "Points to a directory where the run-ptest script is located."
+            </info>
+            <glossdef>
+                <para role="glossdeffirst">
+<!--                <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
+                    Points to a directory where the run-ptest script is located.
+                    This location defaults to the work directory
+                    (<filename><link linkend='var-WORKDIR'>WORKDIR</link></filename>),
+                    but may be overridden within a recipe if a package ships its own run-ptest script.
+                </para>
+            </glossdef>
+        </glossentry>
+
         <glossentry id='var-PV'><glossterm>PV</glossterm>
             <info>
                 PV[doc] = "The version of the recipe. The version is normally extracted from the recipe filename."
Signature · 1 line
1.8.3.1
#2 lore raw
In reply to Ian Ray
Quoted 2 lines

New PTEST_RUN_SCRIPT_PATH allows recipes to override the default location of the run-ptest script.

Please disregard, open-embedded was patched in a simpler way.

Ian