sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Edits to "Compilation" section. 

Added review comments to the section inside the new "Writing
a New Recipe" section.  Minor word fixes.  I did add a new
common compilation failure scenario.  All input from Paul
Eggleton.

(From yocto-docs rev: 5818a8882ff55fc27c5dc77233854465b8c2245b)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-01-09 08:43:50 -06:00 committed by Richard Purdie
parent 814e07159f
commit b6c0bae0aa
1 changed files with 22 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -1876,15 +1876,33 @@
This failure applies to recipes building for the target
or <filename>nativesdk</filename> only.
The failure occurs when the compilation process uses
headers, libraries, or other files from the host system
when the process is cross-compiling for the target and
should not be.</para>
improper headers, libraries, or other files from the
host system during cross-compiling for the target.
</para>
<para>To fix the problem, you should be able to see
the host paths being used (e.g.
<filename>/usr/include</filename>,
<filename>/usr/lib</filename>, and so forth) by
examining the <filename>log.do_configure</filename>
examining the <filename>log.do_compile</filename>
file.</para></listitem>
<listitem><para><emphasis>Failure to find required
libraries/headers:</emphasis>
If a build-time dependency is missing because it has
not been declared in
<ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink>,
or because the dependency exists but the path used by
the build process to find the file is incorrect and the
configure step did not detect it, the compilation
process could fail.
For either of these failures, the compilation process
notes that files could not be found.
In these cases, you need to go back and add additional
options to the configure script as well as possibly
add additional build-time dependencies to
<filename>DEPENDS</filename>.
Occasionally, it is necessary to apply a patch to the
source to ensure the correct paths are used.
</para></listitem>
</itemizedlist>
</para>
</section>