ref-manual, dev-manual: Updates to support PTEST_ENABLED.

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

In the dev-manual, I added a note to the "Adding ptest to Your
Build" section to mention that the OpenEmbedded system uses
PTEST_ENABLED to enable or disable building ptests and that
the user does not set this variable directly.

(From yocto-docs rev: 52d6608caaa25378b873e41e1ddd05356ff8629a)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 10 insertions, 0 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 6aabdf4877..1e4f25d918 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5900,6 +5900,16 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
      DISTRO_FEATURES_append = " ptest"
      EXTRA_IMAGE_FEATURES += "ptest-pkgs"
                     </literallayout>
+                    <note>
+                        The OpenEmbedded build system uses the
+                        <ulink url='&YOCTO_DOCS_REF_URL;#var-PTEST_ENABLED'><filename>PTEST_ENABLED</filename></ulink>
+                        variable to see if it should enable ptests during
+                        a build.
+                        This variable is enabled or disabled through your use
+                        of the <filename>DISTRO_FEATURES</filename> variable.
+                        You do not set <filename>PTEST_ENABLED</filename>
+                        directly.
+                    </note>
                     Once your build is complete, the ptest files are installed
                     into the <filename>/usr/lib/&lt;package&gt;/ptest</filename>
                     directory within the image, where