Comments
Patch
@@ -1,6 +1,7 @@
installdir = "${datadir}/ti"
# This is where do_install will put it
+export C6RUN_INSTALL_DIR_RECIPE = "${installdir}/ti-c6run-tree"
export CODEGEN_INSTALL_DIR_RECIPE = "${installdir}/ti-cgt6x-tree"
export XDC_INSTALL_DIR_RECIPE = "${installdir}/ti-xdctools-tree"
export XDAIS_INSTALL_DIR_RECIPE = "${installdir}/ti-xdais-tree"
@@ -27,6 +28,7 @@ export AUDIO_SOC_INSTALL_DIR_RECIPE =
"${installdir}/ti-audio-soc-example-tree"
export C6ACCEL_INSTALL_DIR_RECIPE = "${installdir}/ti-c6accel-tree"
# This is where the tools will end up in staging provided
PACKAGE_ARCH = ${MACHINE_ARCH} is set
+export C6RUN_INSTALL_DIR =
"${STAGING_DIR}/${MULTIMACH_TARGET_SYS}${C6RUN_INSTALL_DIR_RECIPE}"
I've been putting together some custom bitbake recipes to build dsp apps using c6run. The ti-c6run generates its own compiler to compile the dsp code and I was able to greatly simplify my recipe if I applied the following patch to the ti-paths.inc file in oe. ************************************************************************** export CODEGEN_INSTALL_DIR = "${STAGING_DIR}/${MULTIMACH_TARGET_SYS}${CODEGEN_INSTALL_DIR_RECIPE}" export XDC_INSTALL_DIR = "${STAGING_DIR}/${MULTIMACH_TARGET_SYS}${XDC_INSTALL_DIR_RECIPE}" export XDAIS_INSTALL_DIR = "${STAGING_DIR}/${MULTIMACH_TARGET_SYS}${XDAIS_INSTALL_DIR_RECIPE}" **************************************************************************** This causes all of the native compiling bin tools for the c6run to be installed with all the ti related tools. It also provides a global variable "C6RUN_INSTALL_DIR" that can be used in a custom bitbake recipe to access those tools. The interesting thing is the current ti-c6run recipe file in OE already uses "C6RUN_INSTALL_DIR_RECIPE" if it exists so the ti-path.inc is really the only file that needs to be modified for this all to work. Regards, Shane