-
Notifications
You must be signed in to change notification settings - Fork 1
STAGING_DIR_HOST
Peter Saunderson edited this page Jul 26, 2016
·
2 revisions
Home / parallella-yoctobuild / meta-exotic / Design Guide / Glossary / STAGING_DIR_HOST
STAGING_DIR_HOST
is the default location of the build products in the host file system. The files are staged in specific folders so that when they are installed on a target the appropriate directory structure is created.
STAGING_DIR_TARGET is used to configure the location on the target where the files might be expected.
- state.bbclass: staging_host = d.getVar('STAGING_DIR_HOST', True)
By default the staging location is defined in staging.bbclass and is modified as necessary:
- staging.bbclass: do_populate_sysroot[sstate-outputdirs] = "${STAGING_DIR_HOST}/"
- native.bbclass: do_populate_sysroot[sstate-outputdirs] = "${STAGING_DIR_NATIVE}/"
- libgcc-initial: do_populate_sysroot[sstate-outputdirs] = "${STAGING_DIR_TCBOOTSTRAP}/"
- glibc-initial: do_populate_sysroot[sstate-outputdirs] = "${STAGING_DIR_TCBOOTSTRAP}/"
- gcc-cross-initial: do_populate_sysroot[sstate-outputdirs] = "${STAGING_DIR_HOST}/ ${STAGING_DIR_TCBOOTSTRAP}/${target_base_libdir}/"
To complicate things the value of STAGING_DIR_HOST
and the other variables may also be changed:
- bitbake.conf: STAGING_DIR_HOST = "${STAGING_DIR}/${MACHINE}"
- native.bbclass: STAGING_DIR_HOST = ""
- cross.bbclass: STAGING_DIR_HOST = "${STAGING_DIR}/${HOST_ARCH}${HOST_VENDOR}-${HOST_OS}"
- multilib.conf: STAGING_DIR_HOST = "${STAGING_DIR}/${MLPREFIX}${MACHINE}"
- nativesdk.bbclass: STAGING_DIR_HOST = "${STAGING_DIR}/${MULTIMACH_HOST_SYS}"
- cross-canadian.bbclass: STAGING_DIR_HOST = "${STAGING_DIR}/${HOST_ARCH}-${SDKPKGSUFFIX}${HOST_VENDOR}-${HOST_OS}"