And replaced it by the features that was below it.
see:
commit 43b8b3fa72d75d8d82a478613a4d9bf4645b5389
Author: Ross Burton <ross.burton@arm.com>
Date: Thu Nov 7 13:47:52 2024 +0000
classes-recipe/core-image: drop debug-tweaks IMAGE_FEATURE
Remove the 'debug-tweaks' IMAGE_FEATURE. It sounds friendly and kind to
developers, but it results primarily in an image which root can login
remotely without a password. This is incredibly useful for local
development and testing purposes, but we really want to be explicit that
this is what is happening instead of hiding it behind a vague "debug
tweaks" statement.
To preserve the eixsting behaviour, debug-tweaks should be replaced with
these features:
allow-empty-password empty-root-password allow-root-login post-install-logging
(From OE-Core rev: 2c229f9542c6ba608912e14c9c3f783c3fa89349)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Fixed the warning from kas:
WARNING - Using deprecated refspec for repository "poky". You should migrate to commit/tag/branch.
WARNING - Using deprecated refspec for repository "meta-openembedded". You should migrate to commit/tag/branch.
WARNING - Using deprecated refspec for repository "meta-qt5". You should migrate to commit/tag/branch.
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Since commit 5452f1ba337685cf89d3429e08255450ab90b96f ("local.conf.sample: Bump version so users update their config") in OE-Core,
we need to update the default local.conf due to the new syntax.
Fixes:
ERROR: Error executing a python function in exec_python_func() autogenerated:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
0001:
*** 0002:oecore_update_localconf(d)
0003:
File: '/work/poky/meta/classes/sanity.bbclass', lineno: 56, function: oecore_update_localconf
0052:
0053:is a good way to visualise the changes."""
0054: failmsg = d.expand(failmsg)
0055:
*** 0056: raise NotImplementedError(failmsg)
0057:}
0058:
0059:SANITY_SITECONF_SAMPLE ?= "${COREBASE}/meta*/conf/site.conf.sample"
0060:python oecore_update_siteconf() {
Exception: NotImplementedError: Your version of local.conf was generated from an older/newer version of
local.conf.sample and there have been updates made to this file. Please compare the two
files and merge any changes before continuing.
Matching the version numbers will remove this message.
"meld conf/local.conf /work/poky/meta*/conf/local.conf.sample"
is a good way to visualise the changes.
Signed-off-by: Pierre-Jean Texier <texier.pj2@gmail.com>
The kas tool provides an easy mechanism to setup bitbake based projects.
As explained in [1] the key features provided by kas are:
- clone and checkout bitbake layers
- create default bitbake settings (machine, arch, ...)
- launch minimal build environment, reducing risk of host contamination
- initiate bitbake build process
So, let's create a minimal example in this layer to build an image with a
small effort. This seems interesting for new users of the meta-raspberrypi.
For example:
$: sudo pip3 install kas
$: mkdir rpi
$: cd rpi
$: git clone https://github.com/agherzan/meta-raspberrypi.git
$: kas build meta-raspberrypi/kas-poky-rpi.yml
and that's all !
To adjust the construction with specific options (I2C, SPI, ...), simply add
a section as follows:
local_conf_header:
rpi-specific: |
ENABLE_I2C = "1"
RPI_EXTRA_CONFIG = "dtoverlay=pi3-disable-bt"
To configure the machine, the user have to update the 'machine' variable.
And the same for the 'distro'.
[1] - https://kas.readthedocs.io/en/1.0/userguide.html
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
