Why do you need to repeatedly include the same sources in various recipes? Are you rebuilding the same software over and over again? If not then why aren't the headers and libraries sufficient.
> -----Original Message----- > From: meta-ti-boun...@yoctoproject.org [mailto:meta-ti- > boun...@yoctoproject.org] On Behalf Of Stiffler, Jacob > Sent: Thursday, February 26, 2015 7:34 AM > To: meta-ti@yoctoproject.org > Subject: [meta-ti] [RFC PATCH 4/6] opencl-monitor: OpenCL firmware which > runs on the accelerators. > > Signed-off-by: Jacob Stiffler <j-stiff...@ti.com> > --- > recipes-ti/ocl/opencl-monitor_git.bb | 41 > ++++++++++++++++++++++++++++++++++ > 1 file changed, 41 insertions(+) > create mode 100644 recipes-ti/ocl/opencl-monitor_git.bb > > diff --git a/recipes-ti/ocl/opencl-monitor_git.bb b/recipes-ti/ocl/opencl- > monitor_git.bb > new file mode 100644 > index 0000000..54b3f45 > --- /dev/null > +++ b/recipes-ti/ocl/opencl-monitor_git.bb > @@ -0,0 +1,41 @@ > +DESCRIPTION = "TI OpenCL" > +HOMEPAGE = "https://gitorious.design.ti.com/ocl"; > +LICENSE = "BSD" > + > +include ocl.inc > + > +inherit cmake > + > +COMPATIBLE_MACHINE = "dra7xx" > +PACKAGE_ARCH = "${MACHINE_ARCH}" > + > +SRC_URI_append = " \ > + ${SRC_URI_OPENCL} \ > + ${SRC_URI_MONITOR} \ > + ${SRC_URI_BUILTINS} \ > + ${SRC_URI_LIBM} \ > + ${SRC_URI_MONITOR_IMAGE} \ > + ${MONITOR_PATCHES} \ > + ${OPENCL_PATCHES} \ > + ${OPENGL_HEADERS} \ > +" > + > +S = "${WORKDIR}/git/opencl_monitor" > + > + > +do_compile_append() { > + cp -rv ${WORKDIR}/opencl_monitor-vayu-0.12.0/* ${S}/ } > + > +do_install_append() { > + cp -v ${D}${datadir}/ti/opencl/dsp0.out ${D}${datadir}/ti/opencl/dsp.out > + cp -v ${D}${datadir}/ti/opencl/dsp0.syms > +${D}${datadir}/ti/opencl/dsp.syms } > + > +FILES_${PN} += " \ > + ${datadir}/ti/opencl/* \ > + ${base_libdir}/firmware/* \ > +" > + > +INSANE_SKIP_${PN} = "arch" > + > -- > 1.7.9.5 > > -- > _______________________________________________ > meta-ti mailing list > meta-ti@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-ti -- _______________________________________________ meta-ti mailing list meta-ti@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-ti
