Difference between revisions of "Legacy staging"
From Openembedded.org
PaulEggleton (talk | contribs) (Update for OE-Core and tidy up formatting) |
PaulEggleton (talk | contribs) (tweak) |
||
Line 5: | Line 5: | ||
Steps for moving script code in the <code>do_stage</code> function to the <code>do_install</code> function: | Steps for moving script code in the <code>do_stage</code> function to the <code>do_install</code> function: | ||
− | + | # Move the lines in <code>do_stage</code> to <code>do_install</code>, deleting anything that is already handled in the existing <code>do_install</code> | |
− | + | # Replace <code>STAGING_BINDIR</code> with <code>${D}${bindir}</code> | |
− | + | # Replace <code>STAGING_INCDIR</code> with <code>${D}${includedir}</code> | |
− | + | # Replace <code>STAGING_LIBDIR</code> with <code>${D}${libdir}</code> | |
+ | # Replace <code>STAGING_DATADIR</code> with <code>${D}${datadir}</code> |
Latest revision as of 14:41, 7 November 2012
The term "legacy staging" refers to recipes or classes which have a do_stage
function for populating the sysroot directories that we use for building, rather than having a do_install
that works, along with post install functions to mangle the contents as needed.
In OpenEmbedded-Classic, legacy staging was deprecated but still supported; but with OE-Core, BitBake will error out during parse if it finds a do_stage
function defined in any recipe, so when migrating a recipe you will need to translate this if present.
Steps for moving script code in the do_stage
function to the do_install
function:
- Move the lines in
do_stage
todo_install
, deleting anything that is already handled in the existingdo_install
- Replace
STAGING_BINDIR
with${D}${bindir}
- Replace
STAGING_INCDIR
with${D}${includedir}
- Replace
STAGING_LIBDIR
with${D}${libdir}
- Replace
STAGING_DATADIR
with${D}${datadir}