From: Jared Weyer <jweyer@aecontrols.com>
To: Gyorgy Sarvari <skandigraun@gmail.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
Alexander Kanavin <alex.kanavin@gmail.com>
Subject: Re: [yocto] Issues with DEPENDS
Date: Thu, 23 Oct 2025 15:57:13 +0000 [thread overview]
Message-ID: <1761234983964.30308@aecontrols.com> (raw)
In-Reply-To: <f4a20a19-96ec-4bb4-b105-ea20caf48187@gmail.com>
Hi all,
Thanks for the input! I figured out that the issue was indeed related to the install directory. I have the following in recipe B:
do_install() {
install -d ${D}${MCU_PLUS_SDK_AM263PX_INSTALL_DIR}
cp -r ${B}/. ${D}${MCU_PLUS_SDK_AM263PX_INSTALL_DIR}
}
where MCU_PLUS_SDK_AM263PX_INSTALL_DIR came from two different include files:
# meta-ti/meta-ti-extras/recipes-ti/includes/ti-paths.inc
installdir = "${datadir}/ti"
# meta-aec/recipes-ti/includes/aec-ti-paths.inc
CU_PLUS_SDK_AM263PX_VERSION := "11.00.00.19"
MCU_PLUS_SDK_AM263PX_INSTALL_NAME := "mcu_plus_sdk_am263px_${MCU_PLUS_SDK_AM263PX_VERSION}"
MCU_PLUS_SDK_AM263PX_INSTALL_DIR = "${installdir}/${MCU_PLUS_SDK_AM263PX_INSTALL_NAME}"
The above works as expected; However, the bug was that I had the following:
MCU_PLUS_SDK_AM263PX_INSTALL_DIR := "${installdir}/${MCU_PLUS_SDK_AM263PX_INSTALL_NAME}"
I was using immediate expansion which causing issues only when the recipe was built as a dependency to another recipe. I believe this was because of the context shift causing ${datadir} to expand differently when the recipe was built independently, though I am still not entirely sure why it caused sysroot-components to be empty, I would have expected it to populate but with an incorrect path.
Anyways, thank you both for your input!
Thanks again,
- Jared
________________________________________
From: Gyorgy Sarvari <skandigraun@gmail.com>
Sent: Thursday, October 23, 2025 4:27 AM
To: yocto@lists.yoctoproject.org; Jared Weyer
Subject: Re: [yocto] Issues with DEPENDS
On 10/21/25 03:02, Jared Weyer via lists.yoctoproject.org wrote:
>
> install -m 0755 ${S}/test.txt ${D}/usr/share/ti
> install -m 0755 ${S}/test2.txt ${D}/usr
I remember this, this is how I learned to use bitbake variables for all
paths, I spent at least 2 days debugging it some years ago.
When you do build for native, ${D} is pretty much the same as for
tagret, but ${datadir and ${prefix} are very different.
For target it looks like this:
prefix = /usr
datadir = /usr/share
For native, it looks like this:
prefix =
/home/mee/stuff/ptest-images/build/tmp/work/x86_64-linux/openssl-native/3.5.4/recipe-sysroot-native/usr
datadir =
/home/mee/stuff/ptest-images/build/tmp/work/x86_64-linux/openssl-native/3.5.4/recipe-sysroot-native/usr/share
Try in your recipe you should always use ${D}${datadir}, ${D}{prefix}
etc variables when installing files to avoid such issues.
prev parent reply other threads:[~2025-10-23 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 1:02 Issues with DEPENDS Jared Weyer
2025-10-23 10:39 ` [yocto] " Alexander Kanavin
2025-10-23 11:27 ` Gyorgy Sarvari
2025-10-23 15:57 ` Jared Weyer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1761234983964.30308@aecontrols.com \
--to=jweyer@aecontrols.com \
--cc=alex.kanavin@gmail.com \
--cc=skandigraun@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.