In those cases, our recipe should inherit the allarch class that is inherited by recipes that do not produce architecture-specific output.
An example of this type of recipe, meta-custom/recipes-example/example-data/example-data_1.0.bb, may be seen here:
DESCRIPTION = "Example of data or configuration recipe" SECTION = "examples"
LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
SRCREV = "${AUTOREV}" SRC_URI = "git://github.com/yoctocookbook2ndedition/examples.git file://example.data"
S = "${WORKDIR}/git" inherit allarch do_compile[noexec] = "1"
do_install() { install -d ${D}${sysconfdir} install -d ${D}${sbindir} install -m 0755 ${WORKDIR}/example.data ${D}/${sysconfdir}/ install -m 0755 ${S}/python-scripts/* ${D}/${sbindir} }
It assumes that the fictitious examples.git repository contains a python-scripts folder, which we want to include in our root filesystem.
A working recipe example can be found in the source that accompanies the book.