bit bake error :do_package_qa: QA Issue

[yuxuan]

Hi,

I met "do_package_qa: QA Issue:" error when I  try to update my lib file by adding version and soft link. The specific problems are asfollows:

<packagename> requires <files>, but no providers in its RDEPENDS [file-rdeps]

I have add RDEPENS_${PN} in bb,but the error is still exits.

[Daniel-Aguirre]

Hi,

Could you tell us which S32G platform are you using? Also, which NXP provided BSP version are you working with?

Have you stumble across this message following the user guide?

Please, let us know.

[yuxuan]

Hi Daniel,

Thank you for your relpy.

My S32G platform is s32gen1 and BSP version is 34.

When I want to add version on my dynamic library name,I encountered this problems. I find that there is no error when I bitbake my dynamic library but when I bitbake my test procedure appear that log.

do_package_qa: QA Issue: /data/ts_tool/ipc-shm-uio-test contained in package ipc-shm-uio-test requires libipc-shm-uio-if.so()(64bit), but no providers found in RDEPENDS_ipc-shm-uio-test? [file-rdeps]

I don't know much about yocto，I have add RDEPENDS _${PN} in test procedure bb and this is my dynamic library bb.

FILESEXTRAPATHS_append := "${THISDIR}:"
SRC_URI = "file://${BPN}"

S = "${WORKDIR}/${BPN}"

DEPENDS = "ipc-shm-us"
RDEPENDS_${PN} = ""

INHIBIT_PACKAGE_STRIP = "1"
FILES_${PN} += "${libdir}/lib${BPN}.so.${PV} ${libdir}/lib${BPN}.so"
FILES_${PN}-dev += "${libdir}/lib${BPN}.so.${PV}"
FILES_SOLIBSDEV = ""
BBCLASSEXTEND = "native nativesdk"

LDFLAGS += " -shared"
CFLAGS += " -Werror -g -fPIC -I${STAGING_INCDIR}"

export LDLIBS := " -lipc-shm -lpthread -lrt"

do_compile() {
make MACHINE=${MACHINE} TARGET=lib${BPN}.so.${PV}
}

do_install() {
install -d ${D}${libdir}
install -m 0755 lib${BPN}.so.${PV} ${D}${libdir}
ln -s lib${BPN}.so.${PV} ${D}${libdir}/lib${BPN}.so
}

[Daniel-Aguirre]

Thanks for the information.

Are you following any user guide provided for this BSP version? At this moment, BSP34 is not publicly released, for which we do recommend sending this inquiry to your local NXP representative, for them to use the correct channel.

Said this, there is another community thread that is similar to yours, could be that their solution is similar to yours.

Solved: how to add shared library to recipes - NXP Community

Please, let us know if this information was helpful or not.