Skip to contentSkip to conversation

Documentation: Add examples to User Manual, Metadata chapter

PATCH In review Robert P. J. Day 2 participants 2 messages Jul 9, 2014 – Jul 10, 2014

lore
Share & tools
lore

Robert P. J. Day

author
#0 lore raw

PATCH 1/1 Documentation: Add examples to User Manual, Metadata chapter

Signed-off-by Robert P. J. Day <[email protected]>

---

as long as i've understood everything correctly, this is just
throwing in some physical examples of a couple concepts.

doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +23 -1
index a9f5072..423d9a4 100644
@@ -285,6 +285,16 @@
                 The flags are immediately set to "abc" and "123", respectively.
                 The <filename>a</filename> flag becomes "abc456".
             </para>
+
+            <para>
+                Note that there is no need to pre-define variable flags; you
+                can simply start using them.  One extremely common application
+                is to attach some brief documentation to a BitBake variable as
+                follows:
+                <literallayout class='monospaced'>
+    CACHE[doc] = "The directory holding the cache of the metadata."
+                </literallayout>
+            </para>
         </section>
 
         <section id='inline-python-variable-expansion'>

@@ -298,7 +308,19 @@
      DATE = "${@time.strftime('%Y%m%d',time.gmtime())}"
                 </literallayout>
                 This example results in the <filename>DATE</filename>
-                variable becoming the current date.
+                variable being set to the current date.
+            </para>
+
+            <para>
+                Probably the most common use of this feature is to extract
+                the value of variables from BitBake's internal data dictionary,
+                <filename>d</filename>. The following lines
+                select the values of, respectively, a package name and its
+                version number:
+                <literallayout class='monospaced'>
+    PN = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[0] or 'defaultpkgname'}"
+    PV = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[1] or '1.0'}"
+                </literallayout>
             </para>
         </section>
Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#1 lore raw

Applied with a bit of rewording and whitespace correction for the example. Change needs to be merged to the bitbake repo.

Scott

Quoted 78 lines

-----Original Message-----
From: [email protected] [mailto:bitbake- [email protected]] On Behalf Of Robert P. J. Day
Sent: Wednesday, July 09, 2014 5:04 AM
To: BitBake developer list
Subject: [bitbake-devel] [PATCH] Documentation: Add examples to User Manual, Metadata chapter

Signed-off-by Robert P. J. Day <[email protected]>

---

as long as i've understood everything correctly, this is just throwing in some
physical examples of a couple concepts.

doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +21 -1
index a9f5072..423d9a4 100644
@@ -285,6 +285,16 @@
                The flags are immediately set to "abc" and "123", respectively.
                The <filename>a</filename> flag becomes "abc456".
            </para>
+
+            <para>
+                Note that there is no need to pre-define variable flags; you
+                can simply start using them.  One extremely common application
+                is to attach some brief documentation to a BitBake variable as
+                follows:
+                <literallayout class='monospaced'>
+    CACHE[doc] = "The directory holding the cache of the metadata."
+                </literallayout>
+            </para>
        </section>
 
        <section id='inline-python-variable-expansion'>

@@ -298,7 +308,19 @@
     DATE = "${@time.strftime('%Y%m%d',time.gmtime())}"
                </literallayout>
                This example results in the <filename>DATE</filename>
-                variable becoming the current date.
+                variable being set to the current date.
+            </para>
+
+            <para>
+                Probably the most common use of this feature is to extract
+                the value of variables from BitBake's internal data dictionary,
+                <filename>d</filename>. The following lines
+                select the values of, respectively, a package name and its
+                version number:
+                <literallayout class='monospaced'>
+    PN = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[0] or

'defaultpkgname'}"
+ PV = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[1] or
'1.0'}"
+ </literallayout>

            </para>
        </section>

--

===========================================================
=============
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday

===========================================================
=============
--
_______________________________________________
bitbake-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/bitbake-devel