|
|
| Line 1: |
Line 1: |
| The below are some stylistic guidelines to be aware of when importing recipes from OpenEmbedded.
| | #REDIRECT [[Merging Packages from OpenEmbedded]] |
| Note: please be sure to '''always''' attribute OpenEmbedded when you take a recipe from there, even if it is changed heavily. Something like ''based on recipe from OE'' in your commit message should suffice.
| |
| | |
| * Consistent whitespace throughout the file
| |
| * File follows a roughly standard variable order
| |
| * Patches are all documented
| |
| * No legacy staging
| |
| ** where recipe has a custom do_stage function remove is and ensure its do_install covers everything the do_stage did
| |
| * Use BBCLASSEXTEND where possible instead of -native versions
| |
| * No -sdk or -nativesdk packages, use BBCLASSEXTEND
| |
| * pkgconfig .pc files are correct and don't need manual mangling
| |
| ** if its using pkgconfig.bbclass ensure the .pc files are correct, may need a patch. Sure sign is the .pc files have long paths in including the WORKDIR or sysroot paths. They should just have references like "/usr/lib/", i.e. target system paths and pkgconfig will automatically add in the correct sysroot paths as needed.
| |
| * No custom do_configure for autotooled projects
| |
| * Use "make install" where at all possible
| |
| * Remove any BBVERSIONS lines
| |
| * Use RDEPENDS_pacakgename rather than RDEPENDS (same for RRECOMMENDS)
| |
| * Poky generally avoids INC_PR
| |
| * Poky uses a separate file for hashes rather than having them embedded in the recipe, this may be something we want to adopt but is not the current state of play.
| |
| * Use ALTERNATIVE_* Recipe metadata instead of update-alternatives command
| |
