Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!

Difference between revisions of "Common mistakes in a recipe"

From Openembedded.org
Jump to: navigation, search
(New page: 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! * do not use "libiconv" in (R)DEP...)
 
Line 1: Line 1:
 
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!
 
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!
 +
 +
= (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.
 
* do not use "libiconv" in (R)DEPEND, use "virtual/libiconv" instead.  You risk a corrupted TMPDIR and need to restart from scratch.

Revision as of 13:18, 16 May 2009

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!

(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.
  • never use RDEPENDS to drag kernel modules into an image, use RRECOMMENDS instead
Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox