From: Quentin Schulz <quentin.schulz@cherry.de>
To: yocto@lists.yoctoproject.org, emailaddress.ashish@gmail.com
Subject: Re: [yocto] [Basic]: bitbake menuconfig not reflected changes from custom defconfig
Date: Wed, 22 May 2024 19:31:25 +0200 [thread overview]
Message-ID: <19f72e82-fb97-4ac8-94ea-76cb9d2faf1f@cherry.de> (raw)
In-Reply-To: <lh9y.1716395494266320027.qJhp@lists.yoctoproject.org>
Hi Ashish,
On 5/22/24 6:31 PM, emailaddress.ashish via lists.yoctoproject.org wrote:
> You don't often get email from emailaddress.ashish=gmail.com@lists.yoctoproject.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
> Hi All ,
>
> I am trying basic kernel config change using qemuarm64.
> I have modified the config using bitbake -c menuconfig virtual/kernel & and copied it to my custom layer
>
> After doing an cleansstate when i launch bitbake menuconfig i dont see my changes.
> COMMAND: bitbake -c cleansstate virtual/kernel
> COMMAND: bitbake -c menuconfig virtual/kernel
>
> Below is my debug info:
>
> vmmachine@testuser:~/yocto-nanbield/meta-test/recipes-kernel$ tree
> bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
> .
> └── linux
> ├── linux-yocto
> │ └── testdefconfig
Should be named defconfig.
> └── linux-yocto_%.bbappend
>
>
> vmmachine@testuser:~/yocto-nanbield/meta-test/recipes-kernel$ cat linux/linux-yocto_%.bbappend
> FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
> SRC_URI += "file://testdefconfig"
>
Should be file://defconfig
Try with those changes and report afterwards if it still does not work :)
Cheers,
Quentin
prev parent reply other threads:[~2024-05-22 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 16:31 [Basic]: bitbake menuconfig not reflected changes from custom defconfig emailaddress.ashish
2024-05-22 17:31 ` Quentin Schulz [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=19f72e82-fb97-4ac8-94ea-76cb9d2faf1f@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=emailaddress.ashish@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).