Hello Alexander,
Thank you for your comments. I tried the below sequence of commands and
still could not see anything generated for include or library files.
bitbake -c clean marvell-umsd
bitbake -c clean -f marvell-umsd
bitbake -c cleansstate marvell-umsd
rm -rf sstate-cache/
sbaby@eadlng-build-machine:~/workspace/05222024_simon/ecp-nic-test/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/marvell-umsd/3.0.7-r0$
ls
configure.sstate deploy-source-date-epoch license-destdir packages-split
pkgdata-pdata-input pseudo recipe-sysroot-native
sysroot-destdir UMSD_v3.0.7
deploy-ipks image package pkgdata
pkgdata-sysroot recipe-sysroot source-date-epoch temp
My recipe does not have do_install() but it has do_stage() function. Where
are those files generated? (Marked in bold below)
do_stage () {
mkdir -p ${STAGING_INCDIR}/marvell-umsd
*cp --dereference -R ${MSD_ROOT}/include/*
${STAGING_INCDIR}/marvell-umsd/*
* cp ${MSD_ROOT}/library/msdDrv.o ${STAGING_LIBDIR}*
}
Regards
Simon
On Sat, Jun 1, 2024 at 3:10 AM Alexander Kanavin <alex.kana...@gmail.com>
wrote:
> The folders indicate that the build happened entirely from sstate, and
> so only the sstate objects for populate_sysroot and package_write_ipk
> tasks were executed. You need to use -c cleansstate first and rerun
> it.
>
> Alex
>
> On Sat, 1 Jun 2024 at 00:17, SIMON BABY via lists.yoctoproject.org
> <simonkbaby=gmail....@lists.yoctoproject.org> wrote:
> >
> > Hei Team,
> >
> > I have a recipe below. I did not see the staging directory under the tmp
> generated folder. Is there a hidden folder or where are the files going?
> >
> >
> > DESCRIPTION = "UMSD SDK library for Marvell Switch Product Family."
> > LICENSE = "CLOSED"
> > PR = "r0"
> > PROVIDES = "marvell-umsd"
> > SRC_URI = "file://UMSD_v${PV}.tar.gz"
> >
> > S = "${WORKDIR}/UMSD_v${PV}"
> >
> > MSD_ROOT="${S}"
> > MSD_USER_BASE="${MSD_ROOT}"
> > MSD_PROJ_NAME="msdDrv"
> > MSD_TOOL_DIR="${MSD_USER_BASE}/tools"
> > RELEASE="YES"
> > OS_RUN="LINUX"
> > TOPAZ_BUILD="YES"
> > PERIDOT_BUILD="YES"
> > AGATE_BUILD="YES"
> > PEARL_BUILD="YES"
> > AMETHYST_BUILD="YES"
> > export STAGING_INCDIR
> > export STAGING_LIBDIR
> >
> > do_compile () {
> > make -C ${MSD_ROOT}/src MSD_USER_BASE=${MSD_USER_BASE}/
> MSD_PROJ_NAME=msdDrv MSD_TOOL_DIR="${MSD_USER_BASE}/tools" RELEASE=YES
> OS_RUN:=LINUX PERIDOT_BUILD=YES
> > }
> >
> >
> > do_stage () {
> > mkdir -p ${STAGING_INCDIR}/marvell-umsd
> > cp --dereference -R ${MSD_ROOT}/include/*
> ${STAGING_INCDIR}/marvell-umsd/
> > cp ${MSD_ROOT}/library/msdDrv.o ${STAGING_LIBDIR}
> > }
> >
> >
> >
> > I checked the path below and could not see the include files or the
> msdDrv.o copied anywhere. Please correct me with any other solution. Can I
> go with do_install () ?
> > The requirement is to use this recipe as a dependency for other modules
> to use the include file and library.
> >
> > sbaby@eadlng-build-machine:~/workspace/05222024_simon/ecp-nic-test/build$
> ls -ll
> tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/marvell-umsd/3.0.7-r0/
> > total 40
> > drwxr-xr-x 3 sbaby sbaby 4096 May 29 10:46 deploy-ipks
> > drwxr-xr-x 3 sbaby sbaby 4096 May 29 10:46 license-destdir
> > drwxr-xr-x 7 sbaby sbaby 4096 May 29 10:46 pkgdata-pdata-input
> > drwxr-xr-x 2 sbaby sbaby 4096 May 29 14:52 sstate-install-packagedata
> > drwxr-xr-x 2 sbaby sbaby 4096 May 29 14:52 sstate-install-package_qa
> > drwxr-xr-x 2 sbaby sbaby 4096 May 29 14:52
> sstate-install-package_write_ipk
> > drwxr-xr-x 2 sbaby sbaby 4096 May 29 14:52 sstate-install-populate_lic
> > drwxr-xr-x 2 sbaby sbaby 4096 May 29 14:52
> sstate-install-populate_sysroot
> > drwxr-xr-x 3 sbaby sbaby 4096 May 29 10:46 sysroot-destdir
> > drwxr-xr-x 2 sbaby sbaby 4096 May 29 14:52 temp
> >
> > Regards
> > Simon
> >
> >
> >
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63263): https://lists.yoctoproject.org/g/yocto/message/63263
Mute This Topic: https://lists.yoctoproject.org/mt/106417703/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
