diff options
| -rw-r--r-- | documentation/ref-manual/usingpoky.xml | 59 |
1 files changed, 0 insertions, 59 deletions
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index d4c7127a12..d08031617b 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml | |||
| @@ -736,65 +736,6 @@ | |||
| 736 | </para> | 736 | </para> |
| 737 | </section> | 737 | </section> |
| 738 | 738 | ||
| 739 | <section id='checking-for-missing-build-time-dependencies'> | ||
| 740 | <title>Checking for Missing Build-Time Dependencies</title> | ||
| 741 | |||
| 742 | <para> | ||
| 743 | A recipe might build successfully even though some of its | ||
| 744 | build-time dependencies are missing from | ||
| 745 | <link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>. | ||
| 746 | Following are the two most common ways in which that can happen: | ||
| 747 | <itemizedlist> | ||
| 748 | <listitem><para> | ||
| 749 | The build-time dependency just happens to already exist in | ||
| 750 | the staging sysroot | ||
| 751 | (<link linkend='var-STAGING_DIR_HOST'><filename>STAGING_DIR_HOST</filename></link>) | ||
| 752 | by the time the recipe is built. | ||
| 753 | This situation occurs when the build-time dependency is | ||
| 754 | built earlier during recipe processing. | ||
| 755 | </para></listitem> | ||
| 756 | <listitem><para> | ||
| 757 | The component built by the recipe conditionally enables | ||
| 758 | functionality depending on whether it can find the | ||
| 759 | build-time dependency in the staging sysroot. | ||
| 760 | If the build-time dependency is missing, the corresponding | ||
| 761 | functionality is disabled. | ||
| 762 | This condition is known as a "floating dependency". | ||
| 763 | </para></listitem> | ||
| 764 | </itemizedlist> | ||
| 765 | </para> | ||
| 766 | |||
| 767 | <para> | ||
| 768 | Because dealing with the second case is more complex, focus will | ||
| 769 | be on the first case. | ||
| 770 | The | ||
| 771 | <link linkend='ref-classes-insane'><filename>build-deps</filename></link> | ||
| 772 | QA check checks that every library the component linked against is | ||
| 773 | declared as a build-time dependency. | ||
| 774 | If that is not the case, then the first situation described in the | ||
| 775 | previous list exists, and <filename>build-deps</filename> reports | ||
| 776 | a missing build-time dependency. | ||
| 777 | </para> | ||
| 778 | |||
| 779 | <para> | ||
| 780 | Another, more manual, way to check a recipe for missing build-time | ||
| 781 | dependencies of the first type is to build with an empty staging | ||
| 782 | sysroot. | ||
| 783 | This method can also find missing build-time dependencies | ||
| 784 | that are not in the form of libraries, which the | ||
| 785 | <filename>build-deps</filename> QA check is unable to find. | ||
| 786 | </para> | ||
| 787 | |||
| 788 | <para> | ||
| 789 | An easy way to empty the staging sysroots is to simply remove | ||
| 790 | <link linkend='var-TMPDIR'><filename>TMPDIR</filename></link>, | ||
| 791 | which is usually | ||
| 792 | <filename>${</filename><link linkend='var-BUILDDIR'><filename>BUILDDIR</filename></link><filename>}/tmp</filename>, | ||
| 793 | as it includes the staging sysroots. | ||
| 794 | </para> | ||
| 795 | |||
| 796 | </section> | ||
| 797 | |||
| 798 | <section id='usingpoky-debugging-bitbake'> | 739 | <section id='usingpoky-debugging-bitbake'> |
| 799 | <title>General BitBake Problems</title> | 740 | <title>General BitBake Problems</title> |
| 800 | 741 | ||