Difference between revisions of "Common mistakes in a recipe"

From Openembedded.org
Jump to: navigation, search
m (Reverted edits by Ejumuvo (Talk) to last revision by 75.172.121.11)
 
(3 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
= (R)DEPENDS, etc. =
 
= (R)DEPENDS, etc. =
  
* do not use "libiconv" in (R)DEPEND, use "virtual/libiconv" instead. You risk a corrupted TMPDIR and need to restart from scratch.
+
libiconv in (R)DEPENDS
* never use RDEPENDS to drag kernel modules into an image, use RRECOMMENDS instead
+
: Use "virtual/libiconv" instead as glibc based systems already have libiconv functionality from glibc. Uclibc based systems will get it from "libiconv". By building libiconv in glibc build You risk a corrupted TMPDIR which will need to be restarted from scratch.
 +
 
 +
kernel modules in RDEPENDS
 +
: Never use RDEPENDS to drag kernel modules into an image, use RRECOMMENDS instead. The reason is that some devices can have those modules built-in into kernel.
  
 
[[Category:Dev]]
 
[[Category:Dev]]
 
[[Category:FAQ]]
 
[[Category:FAQ]]

Latest revision as of 09:41, 24 November 2010

This page should list common (!) mistakes when defining a recipe. a link or one sentence explaining what the problem is are a bonus. But keep it short!

[edit] (R)DEPENDS, etc.

libiconv in (R)DEPENDS

Use "virtual/libiconv" instead as glibc based systems already have libiconv functionality from glibc. Uclibc based systems will get it from "libiconv". By building libiconv in glibc build You risk a corrupted TMPDIR which will need to be restarted from scratch.

kernel modules in RDEPENDS

Never use RDEPENDS to drag kernel modules into an image, use RRECOMMENDS instead. The reason is that some devices can have those modules built-in into kernel.
Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox