Whats the standard macro for "${WORKDIR}/sources" in master branch

Whats the standard macro for "${WORKDIR}/sources" in master branch

[AshishKumar Mishra]

[-- 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 --]

Re: [oe] Whats the standard macro for "${WORKDIR}/sources" in master branch

[Gyorgy Sarvari]

I think you are looking for ${UNPACKDIR} [1]

[1]:
https://git.openembedded.org/openembedded-core/tree/meta/conf/bitbake.conf#n410

On 10/30/25 11:22, AshishKumar Mishra via lists.openembedded.org wrote:
> 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 
>  
>  
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#121204): https://lists.openembedded.org/g/openembedded-devel/message/121204
> Mute This Topic: https://lists.openembedded.org/mt/116027483/6084445
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: Whats the standard macro for "${WORKDIR}/sources" in master branch

[AshishKumar Mishra]

[-- Attachment #1: Type: text/plain, Size: 28 bytes --]

Thanks a lot !

- Ashish

[-- Attachment #2: Type: text/html, Size: 85 bytes --]