From: "AshishKumar Mishra" <ashishkumar.mishra@bmwtechworks.in>
To: openembedded-devel@lists.openembedded.org
Subject: Whats the standard macro for "${WORKDIR}/sources" in master branch
Date: Thu, 30 Oct 2025 03:22:32 -0700 [thread overview]
Message-ID: <aylY.1761819752207315631.fowC@lists.openembedded.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hi Team ,
We used to have the file added via SRC_URI in well known macro relative to ${WORKDIR} & have standard macro's
But in master the files are placed under *"${WORKDIR}/sources"*
Example for imagemagick:
P="imagemagick-7.1.2-5"
S="/mnt/addon-drive/00-upstream/master/build/tmp/work/x86-64-v3-poky-linux/imagemagick/7.1.2-5/sources/imagemagick-7.1.2-5"
WORKDIR="/mnt/addon-drive/00-upstream/master/build/tmp/work/x86-64-v3-poky-linux/imagemagick/7.1.2-5"
00-upstream/master/build : ls -al 00-upstream/master/build/tmp/work/x86-64-v3-poky-linux */imagemagick/7.1.2-5/sources/*
total 20
drwxr-xr-x 3 bti-001003 domain users 4096 Oct 30 15:08 .
drwxr-xr-x 20 bti-001003 domain users 4096 Oct 30 15:29 ..
drwxr-xr-x 22 bti-001003 domain users 4096 Oct 30 15:08 *imagemagick-7.1.2-5*
-rwxr-xr-x 1 bti-001003 domain users 3679 Oct 30 15:07 *imagemagick-ptest.sh*
-rw-r--r-- 1 bti-001003 domain users 962 Oct 29 17:50 *run-ptest*
so in recipe we have to make use either of :
- ${S}/ *..* /run-ptest
- ${WORKDIR}/ *sources* /run-ptest
i am naturally aligned for approach (b) from above
a) But wanted to check what's the preferred way from community ?
b) Or if we have any standard macro for ${WORKDIR}/sources to be used in recipe
c) Or if members are expecting a new macro to be created ?
Thanks ,
Ashish Kumar Mishra
[-- Attachment #2: Type: text/html, Size: 1974 bytes --]
next reply other threads:[~2025-10-30 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 10:22 AshishKumar Mishra [this message]
2025-10-30 10:26 ` [oe] Whats the standard macro for "${WORKDIR}/sources" in master branch Gyorgy Sarvari
2025-10-30 10:29 ` AshishKumar Mishra
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=aylY.1761819752207315631.fowC@lists.openembedded.org \
--to=ashishkumar.mishra@bmwtechworks.in \
--cc=openembedded-devel@lists.openembedded.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.