Well heres the dltwrapper bb file it appears to build fine # # This file was derived from the 'Hello World!' example recipe in the # Yocto Project Development Manual. #
DESCRIPTION = "DLT Wrapper" SECTION = "examples" DEPENDS = "boost libusb1 dlt-daemon" LICENSE = "COMPANY_COMMON_LICENSES" LIC_FILES_CHKSUM = "file://${COMPANY_COMMON_LICENSES}/LICENSE;md5=18f1f6bf24836561f3a65cef19477d20" TARGET_CFLAGS += "-std=gnu++14" # This tells bitbake where to find the files we're providing on the local filesystem FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" FILES_${PN} += "${includedir}/*" inherit autotools gettext cmake # Use local tarball SRC_URI = "file://DLTWrapper.tgz" # Make sure our source directory (for the build) matches the directory structure in the tarball S = "${WORKDIR}/DLTWrapper" do_install() { install -d ${D}${libdir} install -d ${D}${includedir} install -m 0755 ${WORKDIR}/build/libDLTWrapper.so ${D}${libdir} install -m 0755 ${WORKDIR}/DLTWrapper/include/* ${D}${includedir} } On Mon, Mar 12, 2018 at 12:58 PM, Burton, Ross <ross.bur...@intel.com> wrote: > At a guess as I don't have any of your recipes to look at, jsonparser and > dltwrapper packages are broken and putting the libraries into the -dev > packages. That probably caused a QA warning too. > > Ross > > On 12 March 2018 at 11:53, Outback Dingo <outbackdi...@gmail.com> wrote: >> >> ERROR: QA Issue: r4-hub rdepends on dltwrapper-dev [dev-deps] >> ERROR: QA Issue: r4-hub rdepends on jsonparser-dev [dev-deps] >> ERROR: QA run found fatal errors. Please consider fixing them. >> ERROR: Function failed: do_package_qa >> ERROR: Logfile of failure stored in: log.do_package_qa.21297 >> >> seems ive created a bitbake recipe, which depends on a couple of >> libraries to be built, so i created the bitbake for the libs and all >> appears to build fine, however seeing the failure above its basically >> telling me something isnt being created during the packaging process >> for the libs to be properly included in the image, they does exist a >> pkgname-dev.ipkg for each of the libs but not a packagename.ipkg ... >> any ideas... its kind of holding me up at this point. >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto