I think this is a wrong fix. Most settings are just fine.
Please double check.
Regards,
Qi
On 6/3/24 17:03, wangmy via lists.yoctoproject.org wrote:
Replace references of WORKDIR with UNPACKDIR where it makes sense to do so in
preparation for changing the default value of UNPACKDIR.
On 5/29/24 05:31, bibibob...@gmail.com wrote:
Greetings everyone,
Dummy question, is there a quick way to disable bitbake output color?
When we do container build, there is a lot of ANSI color code.
[36m[39m NOTE: recipe python3-gcovr-native-5.1-r0: task
do_autorev_check:
How about using the following setting?
RDEPENDS:${PN} += “sqlite3”
Regards,
Qi
From: yocto@lists.yoctoproject.org On Behalf Of
Alexander Kanavin
Sent: Tuesday, May 14, 2024 4:34 PM
To: salahaldeen.alt...@leica-camera.com; yocto@lists.yoctoproject.org
Subject: Re: [yocto] requires
I haven't tested, but you can try:
In meta-x's layer.conf:
THIS_SPECIFIC_DIR = "${LAYERDIR}"
Then use the variable THIS_SPECIFIC_DIR in other places including meta-y.
Regards,
Qi
On 3/13/24 18:38, Saswati Nayak wrote:
Hello All,
I require guidance on utilizing a file directory
I'd suggest that in the serial console you get:
1) check the ip address of the booted target
2) Run 'ssh root@localhost' on that target to check if login onto itself
is OK
3) If you can ssh locally and the ip is 192.168.7.2, and you still have
problem with 'ssh root@192.168.7.2', maybe you need
From: Chen Qi
For sysvinit with systemd, the systemd package will still be build.
This gives us a warning like below:
WARNING: systemd-1_255.1-r0 do_install: Using /home/root as root
user's home directory is not fully supported by systemd
Set ROOT_HOME to "/root" to avoid such
From: Chen Qi
The default INIT_MANAGER is 'sysvinit', to use systemd as the init
manager, we use INIT_MANAGER = 'systemd' because we can make use
of the settings in conf/distro/include/init-manager-systemd.inc.
Signed-off-by: Chen Qi
---
config.json | 13 +
1 file changed, 5
On 12/29/23 15:38, Gileon Chai wrote:
Thank you for your reply.
HELLO's value in two bbfiles is same when using ':=', but it brought new errors:
ERROR: When reparsing a.bb and b.bb: the basehash value changed from
to . The metadata is not deterministic and this needs to be
fixed.
This
How about using ':='?
e.g.,
HELLO := "${@random_number_function}"
Regards,
Qi
On 12/29/23 13:49, Jiliang Cai wrote:
I define a global variable in config like this:
HELLO=${@random_number_function}
Then I print HELLO's value in two bbfiles. I found that the value of
HELLO is different because
From systemd's source codes (src/oom/oomd-manager.h):
/* Take action if 10s of memory pressure > 60 for more than 30s. We use
the "full" value from PSI so this is the
* percentage of time all tasks were delayed (i.e. unproductive).
* Generally 60 or higher might be acceptable for something
On 9/11/23 15:36, Alexander Kanavin wrote:
On Mon, 11 Sept 2023 at 06:22, Chen Qi via lists.yoctoproject.org
wrote:
SSTATE_DIR and DL_DIR are writable. Sharing them among different builds
owned/controlled by the same user is OK, but sharing these writable
directories among different users
SSTATE_DIR and DL_DIR are writable. Sharing them among different builds
owned/controlled by the same user is OK, but sharing these writable
directories among different users does not seem to be a good idea.
You could consider using the PREMIRRORS and SSTATE_MIRRORS.
Regards,
Qi
On 9/11/23
From: Chen Qi
These two layers do not have oeqa lib modules. Remove these two
lines. Otherwise, `bitbake-layers add-layer ' would fail
if either of these two layers are in BBLAYERS.
Signed-off-by: Chen Qi
---
meta-security-compliance/conf/layer.conf | 2 --
meta-security-isafw/conf/layer.conf
13 matches
Mail list logo
