summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml19
1 files changed, 0 insertions, 19 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 a39438dbf5..5b3bb83d10 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
@@ -653,25 +653,6 @@
653 </para> 653 </para>
654 </section> 654 </section>
655 655
656 <section id='executing-a-list-of-task-and-recipe-combinations'>
657 <title>Executing a List of Task and Recipe Combinations</title>
658
659 <para>
660 The BitBake command line supports specifying different
661 tasks for individual targets when you specify multiple
662 targets.
663 For example, suppose you had two targets (or recipes)
664 <filename>myfirstrecipe</filename> and
665 <filename>mysecondrecipe</filename> and you needed
666 BitBake to run <filename>taskA</filename> for the first
667 recipe and <filename>taskB</filename> for the second
668 recipe:
669 <literallayout class='monospaced'>
670 $ bitbake myfirstrecipe recipe:do_taskA mysecondrecipe recipe:do_taskB
671 </literallayout>
672 </para>
673 </section>
674
675 <section id='generating-dependency-graphs'> 656 <section id='generating-dependency-graphs'>
676 <title>Generating Dependency Graphs</title> 657 <title>Generating Dependency Graphs</title>
677 658