summaryrefslogtreecommitdiffstats
path: root/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
diff options
context:
space:
mode:
Diffstat (limited to 'bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml')
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml19
1 files changed, 19 insertions, 0 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
index 7a37edd509..5b3bb83d10 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
@@ -634,6 +634,25 @@
634 </para> 634 </para>
635 </section> 635 </section>
636 636
637 <section id='executing-a-list-of-task-and-recipe-combinations'>
638 <title>Executing a List of Task and Recipe Combinations</title>
639
640 <para>
641 The BitBake command line supports specifying different
642 tasks for individual targets when you specify multiple
643 targets.
644 For example, suppose you had two targets (or recipes)
645 <filename>myfirstrecipe</filename> and
646 <filename>mysecondrecipe</filename> and you needed
647 BitBake to run <filename>taskA</filename> for the first
648 recipe and <filename>taskB</filename> for the second
649 recipe:
650 <literallayout class='monospaced'>
651 $ bitbake myfirstrecipe recipe:do_taskA mysecondrecipe recipe:do_taskB
652 </literallayout>
653 </para>
654 </section>
655
637 <section id='generating-dependency-graphs'> 656 <section id='generating-dependency-graphs'>
638 <title>Generating Dependency Graphs</title> 657 <title>Generating Dependency Graphs</title>
639 658