From: Quentin Schulz <quentin.schulz@cherry.de>
To: yocto@lists.yoctoproject.org, proffesionaladdress2@duck.com,
Gyorgy Sarvari <skandigraun@gmail.com>
Subject: Re: [yocto] warn if a variable is not used
Date: Mon, 14 Apr 2025 12:58:57 +0200 [thread overview]
Message-ID: <5efb98da-5bd9-447d-b193-48d9de275bb8@cherry.de> (raw)
In-Reply-To: <A1FCA99A-D1F4-45C5-9174-3D1F7F2D8082.1@smtp-inbound1.duck.com>
Hi,
On 4/8/25 3:12 PM, proffesionaladdress2 via lists.yoctoproject.org wrote:
> Thank you, but branch is never reached because the previous condition is never true in this code (and I don't know why).
> Even if bbwarn print 'WARNING: rpi-u-boot-scr-1.0-r0 do_compile: isempty=true'.
>
> isempty="${@bb.utils.contains('MY_VARIABLE', '', 'false', 'true', d)}"
> bbwarn "isempty=$isempty"
> if [[ $isempty == true ]]; then
This syntax is not supported by BitBake, please use POSIX condition here
instead. (i.e. not the [[ ]], but [ ]).
Cheers,
Quentin
next prev parent reply other threads:[~2025-04-14 10:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 8:15 Yocto on AMD Zen target ? Joel GUITTET
2025-04-04 9:17 ` [yocto] " Khem Raj
2025-04-04 9:34 ` Alexander Kanavin
2025-04-04 9:36 ` Joel GUITTET
[not found] ` <E63C2FBD-D303-4686-B29D-D8306CB27A80.1@smtp-inbound1.duck.com>
2025-04-08 8:23 ` warn if a variable is not used proffesionaladdress2
2025-04-08 8:58 ` proffesionaladdress2
2025-04-08 8:59 ` proffesionaladdress2
2025-04-08 12:56 ` [yocto] " Gyorgy Sarvari
[not found] ` <7A2D6367-3CD1-460F-9655-69A8B0D980A7.1@smtp-inbound1.duck.com>
[not found] ` <05B9C867-74DD-4A91-9A1B-1BD33302248A.1@smtp-inbound1.duck.com>
2025-04-08 13:09 ` Gyorgy Sarvari
2025-04-08 13:12 ` proffesionaladdress2
2025-04-14 10:58 ` Quentin Schulz [this message]
[not found] ` <8417B008-2B4E-42D4-B5A6-E7D31B7D6D3D.1@smtp-inbound1.duck.com>
2025-04-14 13:57 ` proffesionaladdress2
2025-04-08 13:18 ` Clayton Casciato
[not found] ` <4C0F3047-0C25-4038-BA0C-FE81491D89E5.1@smtp-inbound1.duck.com>
2025-04-09 15:32 ` proffesionaladdress2
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=5efb98da-5bd9-447d-b193-48d9de275bb8@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=proffesionaladdress2@duck.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.