From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: yocto@yoctoproject.org
Cc: Scott Rifenbark <srifenbark@gmail.com>
Subject: [PATCH v2] ref-manual: New WKS_FILE variable glossary entry.
Date: Mon, 12 Dec 2016 14:01:20 +0200 [thread overview]
Message-ID: <1481544080-3515-1-git-send-email-ed.bartosh@linux.intel.com> (raw)
In-Reply-To: <5dcc694b-0fa1-058c-c7a9-7eb5bd4075e0@mender.io>
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
---
documentation/ref-manual/ref-variables.xml | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 4e003cd..9c03364 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -15548,6 +15548,20 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
</glossdef>
</glossentry>
+ <glossentry id='var-WKS_FILE'><glossterm>WKS_FILE</glossterm>
+ <info>
+ WKS_FILE[doc] = "Specifies the name of the wic kickstart file."
+ </info>
+ <glossdef>
+ <para role="glossdeffirst">
+ Specifies the location of the wic kickstart file that is
+ used to <ulink url='&YOCTO_DOCS_DEV_URL;#creating-wic-images-oe'>create wic partitioned image by the OpenEmbedded build system</ulink>.
+ For details on kickstart file format, see
+ <ulink url='&YOCTO_DOCS_DEV_URL;#openembedded-kickstart-wks-reference'>OpenEmbedded Kickstart (.wks) Reference</ulink>.
+ </para>
+ </glossdef>
+ </glossentry>
+
<glossentry id='var-WORKDIR'><glossterm>WORKDIR</glossterm>
<info>
WORKDIR[doc] = "The pathname of the working directory in which the OpenEmbedded build system builds a recipe. This directory is located within the TMPDIR directory structure and changes as different packages are built."
--
2.6.6
prev parent reply other threads:[~2016-12-12 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 12:54 [PATCH] ref-manual: New WKS_FILE variable glossary entry Ed Bartosh
2016-12-09 10:24 ` Kristian Amlie
2016-12-12 12:01 ` Ed Bartosh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1481544080-3515-1-git-send-email-ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=srifenbark@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.