From: Ross Burton <Ross.Burton@arm.com>
To: "<yocto@lists.yoctoproject.org>" <yocto@lists.yoctoproject.org>,
"simonkbaby@gmail.com" <simonkbaby@gmail.com>
Subject: Re: [yocto] packages not generated in output folder
Date: Fri, 17 May 2024 10:50:23 +0000 [thread overview]
Message-ID: <297A0044-BE8B-4470-983F-91529C3F67BF@arm.com> (raw)
In-Reply-To: <CAEFUPH2wugXtmvaVQPWi4Le=5vAKOEr7=9Cn3Nv47WOqHFhE9g@mail.gmail.com>
On 16 May 2024, at 20:28, SIMON BABY via lists.yoctoproject.org <simonkbaby=gmail.com@lists.yoctoproject.org> wrote:
>
> Hello,
>
> I am building some applications in 5.15.0-102-generic #112~20.04.1-Ubuntu. My yocto recipes aeh building successfully but I am unable to see any package folders under the tmp directory. I see only log files under temp are created. Nothing else. Can I know if I am missing any configuration?
>
> tmp/work/cortexa5t2hf-neon-vfpv4-poky-linux-gnueabi/marvell-umsd/3.0.7-r0$ ls -ll
> total 12
> drwxr-xr-x 2 sbaby sbaby 12288 May 16 12:26 temp
>
> This is valid for other recipes as well.
>
> /build/tmp/work/cortexa5t2hf-neon-vfpv4-poky-linux-gnueabi/libgcc/11.4.0-r0$ ls
> temp
If a recipe is pulled from sstate (because it has already been built) or if you have rm_work enabled then that’s expected behaviour. You only have a package/ directory in the work tree if the recipe was literally just re-packaged and rm_work hasn’t deleted it.
Ross
prev parent reply other threads:[~2024-05-17 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 19:28 packages not generated in output folder SIMON BABY
2024-05-16 19:54 ` [yocto] " Martin Jansa
2024-05-16 19:58 ` Khem Raj
2024-05-16 21:06 ` SIMON BABY
2024-05-16 19:55 ` Khem Raj
2024-05-17 10:50 ` Ross Burton [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=297A0044-BE8B-4470-983F-91529C3F67BF@arm.com \
--to=ross.burton@arm.com \
--cc=simonkbaby@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).