Re: [yocto] On managing debug and production builds
Hi Vinayak I believe that the best way to prepare debug and prod images is to create include file (.inc) with base set of packages and features and then add two .bb recipes, one for prod and one for debug - every of this recipes will need to include the `.inc` file. You could name them `base-image-prod.bb` and `base-image-debug.bb`. This way you could run either prod or debug builds by running `bitbake base-image-debug` or `bitbake base-image-prod`. As for the machine, this would need to be set in local.conf every time you want to switch the machine. To simplify this process, for the management of the configuration of the entire build (including the selection of debug / prod image or machine configuration), I recommend the kas[1] project with the very helpful kas-container tool. [1] https://github.com/siemens/kas Regards, Tomasz Żyjewski Embedded Systems Engineer GPG: 5C495EA3EBEECA59 https://3mdeb.com | @3mdeb_com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56332): https://lists.yoctoproject.org/g/yocto/message/56332 Mute This Topic: https://lists.yoctoproject.org/mt/89469781/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
Hello Raj,
yes, you are right, {B} works too, and looks more logical.
Thanks for adapting my patch accordingly.
Many greetings,
Matthias
-Ursprüngliche Nachricht-
Von: Khem Raj
Gesendet: Montag, 28. Februar 2022 18:08
An: Konrad Weihmann
Cc: Matthias Klein ; yocto@lists.yoctoproject.org;
Tim Orling ; Richard Purdie
Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
On Mon, Feb 28, 2022 at 5:10 AM Konrad Weihmann wrote:
>
> Hi Matthias,
>
> you're right :(
>
> PYPA_WHEEL = "${S}/py-smbus/dist/smbus-*-*.whl"
this should be B instead I think
>
> finally does it
>
> @Tim @Richard
> PYPA_WHEEL doesn't respect SETUPTOOLS_SETUP_PATH, which might be
> another issue to fix
>
> BR
> Konrad
>
> On 28.02.22 14:04, Matthias Klein wrote:
> > Hello Konrad,
> >
> > unfortunately it still does not build:
> >
> > ERROR: smbus-*-*.whl is not a valid wheel filename.
> >
> > Best regards,
> > Matthias
> >
> > -Ursprüngliche Nachricht-
> > Von: Konrad Weihmann
> > Gesendet: Montag, 28. Februar 2022 13:59
> > An: Matthias Klein ;
> > yocto@lists.yoctoproject.org
> > Betreff: Re: AW: [yocto] python3-smbus no longer builds - Does anyone have
> > an idea?
> >
> > On 28.02.22 13:56, Matthias Klein wrote:
> >> Hello Konrad,
> >>
> >> Thanks for the quick feedback.
> >>
> >> Have you been able to build the package with the change?
> >> I get a similar error with it:
> >
> > Dang - that's the second issue being open in this series...
> >
> >>
> >> ERROR: smbus-4.3-*.whl is not a valid wheel filename.
> >
> > Try
> >
> > PYPA_WHEEL = "${PIP_INSTALL_DIST_PATH}/smbus-*-*.whl"
> >
> > instead - and it should really work
> >
> >>
> >> Best reagrds,
> >> Matthias
> >>
> >> -Ursprüngliche Nachricht-
> >> Von: Konrad Weihmann
> >> Gesendet: Montag, 28. Februar 2022 13:51
> >> An: Matthias Klein ;
> >> yocto@lists.yoctoproject.org
> >> Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an
> >> idea?
> >>
> >> Hi Matthias,
> >>
> >> this is cause by merged PEP-517 changes.
> >> To make it build again just inject
> >>
> >> PIP_INSTALL_PACKAGE = "smbus"
> >>
> >> into the recipe or a bbappend.
> >> Mainly the python3-prefix of the recipe, makes the name guessing
> >> fail, I suspect patches to be incoming soon
> >>
> >> BR
> >> Konrad
> >>
> >> On 28.02.22 13:45, Matthias Klein wrote:
> >>> Hello,
> >>>
> >>> the python3-smbus package no longer builds.
> >>>
> >>> The install step ends with the following error message:
> >>>
> >>> ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename.
> >>>
> >>> Does anyone have an idea what is the cause?
> >>>
> >>> Many greetings,
> >>>
> >>> Matthias
> >>>
> >>>
> >>>
> >>>
> >>>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56331): https://lists.yoctoproject.org/g/yocto/message/56331
Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Custom Image Type
Thanks, Khem.
On 2/28/22 8:54 PM, Khem Raj wrote:
On Mon, Feb 28, 2022 at 8:32 PM Rudolf J Streif
wrote:
I ran into a problem with a custom image type class. I called the class
image_types_ota.bbclass.
When I try to use it I am getting these error messages for two
predefined image recipes (but only for these two, for any other image
recipe it is fine):
ERROR:
/develop/projects/tcu/build/../poky/meta/recipes-rt/images/core-image-rt-sdk.bb:
No IMAGE_CMD defined for IMAGE_FSTYPES entry 'ota' - possibly invalid
type name or missing support class
ERROR:
/develop/projects/tcu/build/../meta-openembedded/meta-networking/recipes-core/images/meta-networking-image-base.bb:
No IMAGE_CMD defined for IMAGE_FSTYPES entry 'ota' - possibly invalid
type name or missing support class
ERROR: Failed to parse recipe:
/develop/projects/tcu/build/../poky/meta/recipes-rt/images/core-image-rt-sdk.bb
I have no idea what in these two image recipes could trigger this error
message.
hard to tell without knowing how ota class is being plugged in or what
its content is.
Do you define IMAGE_FSTYPES:ota ... somewhere ?
The image class defines IMAGE_CMD. There is not much to it for now:
OTA_ROOTFS_MD5 ?= "rootfs.md5"
IMAGE_CMD:ota () {
build_ota="${WORKDIR}/build-ota"
# rootfs
md5sum ${IMAGE_ROOTFS} > ${build_ota}/OTA_ROOTFS_MD5
}
What I don't see is why these two are the only image recipes this is
occurring with. All the other image recipes do not throw a parser error.
Thanks,
Rudi
--
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3386 x700
OpenPGP_0x8D8CA82927339B75.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56330): https://lists.yoctoproject.org/g/yocto/message/56330
Mute This Topic: https://lists.yoctoproject.org/mt/89469318/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] Custom Image Type
I ran into a problem with a custom image type class. I called the class image_types_ota.bbclass. When I try to use it I am getting these error messages for two predefined image recipes (but only for these two, for any other image recipe it is fine): ERROR: /develop/projects/tcu/build/../poky/meta/recipes-rt/images/core-image-rt-sdk.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'ota' - possibly invalid type name or missing support class ERROR: /develop/projects/tcu/build/../meta-openembedded/meta-networking/recipes-core/images/meta-networking-image-base.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'ota' - possibly invalid type name or missing support class ERROR: Failed to parse recipe: /develop/projects/tcu/build/../poky/meta/recipes-rt/images/core-image-rt-sdk.bb I have no idea what in these two image recipes could trigger this error message. Thanks, Rudi OpenPGP_0x8D8CA82927339B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56327): https://lists.yoctoproject.org/g/yocto/message/56327 Mute This Topic: https://lists.yoctoproject.org/mt/89469318/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] QA notification for completed autobuilder build (yocto-3.3.5.rc1)
Hi Everyone, This is the full report for yocto-3.3.5.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No new issue found. Thanks, Jay > -Original Message- > From: yocto@lists.yoctoproject.org On > Behalf Of Richard Purdie > Sent: Tuesday, 22 February, 2022 5:51 PM > To: > Cc: qa-build-notification > Subject: [yocto] QA notification for completed autobuilder build (yocto- > 3.3.5.rc1) > > A build flagged for QA (yocto-3.3.5.rc1) was completed on the autobuilder > and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-3.3.5.rc1 > > > Build hash information: > > bitbake: aaa7f7af23d5f89fe4a5ed48c57ea3dfca07c79d > meta-agl: 9a50bd62dfac0d6ea1320b2ee083529cb98b9f92 > meta-arm: fe35ff5ba809bf4826adfe65899a84e9c99494e8 > meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58 > meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f > meta-intel: 36e915402dfe317654568f09f18fb6f7653603bc > meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e > meta-openembedded: 23598caeafce0af0dde8d1339cf5edff021f6823 > oecore: 29cd1d796057ef5599fe17c39b42aa099f7b1c29 > poky: 8d3e054f6d432b5ca0fcd613e0c767fab3c85f24 > > > > This is an automated message from the Yocto Project Autobuilder > Git: git://git.yoctoproject.org/yocto-autobuilder2 > Email: richard.pur...@linuxfoundation.org > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56324): https://lists.yoctoproject.org/g/yocto/message/56324 Mute This Topic: https://lists.yoctoproject.org/mt/89313716/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
On Mon, Feb 28, 2022 at 5:10 AM Konrad Weihmann wrote:
>
> Hi Matthias,
>
> you're right :(
>
> PYPA_WHEEL = "${S}/py-smbus/dist/smbus-*-*.whl"
this should be B instead I think
>
> finally does it
>
> @Tim @Richard
> PYPA_WHEEL doesn't respect SETUPTOOLS_SETUP_PATH, which might be another
> issue to fix
>
> BR
> Konrad
>
> On 28.02.22 14:04, Matthias Klein wrote:
> > Hello Konrad,
> >
> > unfortunately it still does not build:
> >
> > ERROR: smbus-*-*.whl is not a valid wheel filename.
> >
> > Best regards,
> > Matthias
> >
> > -Ursprüngliche Nachricht-
> > Von: Konrad Weihmann
> > Gesendet: Montag, 28. Februar 2022 13:59
> > An: Matthias Klein ;
> > yocto@lists.yoctoproject.org
> > Betreff: Re: AW: [yocto] python3-smbus no longer builds - Does anyone have
> > an idea?
> >
> > On 28.02.22 13:56, Matthias Klein wrote:
> >> Hello Konrad,
> >>
> >> Thanks for the quick feedback.
> >>
> >> Have you been able to build the package with the change?
> >> I get a similar error with it:
> >
> > Dang - that's the second issue being open in this series...
> >
> >>
> >> ERROR: smbus-4.3-*.whl is not a valid wheel filename.
> >
> > Try
> >
> > PYPA_WHEEL = "${PIP_INSTALL_DIST_PATH}/smbus-*-*.whl"
> >
> > instead - and it should really work
> >
> >>
> >> Best reagrds,
> >> Matthias
> >>
> >> -Ursprüngliche Nachricht-
> >> Von: Konrad Weihmann
> >> Gesendet: Montag, 28. Februar 2022 13:51
> >> An: Matthias Klein ;
> >> yocto@lists.yoctoproject.org
> >> Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an
> >> idea?
> >>
> >> Hi Matthias,
> >>
> >> this is cause by merged PEP-517 changes.
> >> To make it build again just inject
> >>
> >> PIP_INSTALL_PACKAGE = "smbus"
> >>
> >> into the recipe or a bbappend.
> >> Mainly the python3-prefix of the recipe, makes the name guessing fail, I
> >> suspect patches to be incoming soon
> >>
> >> BR
> >> Konrad
> >>
> >> On 28.02.22 13:45, Matthias Klein wrote:
> >>> Hello,
> >>>
> >>> the python3-smbus package no longer builds.
> >>>
> >>> The install step ends with the following error message:
> >>>
> >>> ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename.
> >>>
> >>> Does anyone have an idea what is the cause?
> >>>
> >>> Many greetings,
> >>>
> >>> Matthias
> >>>
> >>>
> >>>
> >>>
> >>>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56323): https://lists.yoctoproject.org/g/yocto/message/56323
Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-security][PATCH 1/2] layer.conf: enable apparmor for qemu machine
Signed-off-by: Armin Kuster
---
conf/layer.conf | 3 +++
1 file changed, 3 insertions(+)
diff --git a/conf/layer.conf b/conf/layer.conf
index 1f83593..21f03d1 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -16,3 +16,6 @@ LAYERDEPENDS_security = "core openembedded-layer perl-layer
networking-layer met
# Sanity check for meta-security layer.
# Setting SKIP_META_SECURITY_SANITY_CHECK to "1" would skip the bbappend files
check.
INHERIT += "sanity-meta-security"
+
+QB_KERNEL_CMDLINE_APPEND = " ${@bb.utils.contains('DISTRO_FEATURES',
'apparmor', 'apparmor=1 security=apparmor', '', d)}"
+
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56321): https://lists.yoctoproject.org/g/yocto/message/56321
Mute This Topic: https://lists.yoctoproject.org/mt/89453851/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-security][PATCH 2/2] parsec-service: Only enable TPM is layer and DISTRO_FEATURE is defined.
Signed-off-by: Armin Kuster
---
.../recipes-parsec/parsec-service/parsec-service_0.8.1.bb | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta-parsec/recipes-parsec/parsec-service/parsec-service_0.8.1.bb
b/meta-parsec/recipes-parsec/parsec-service/parsec-service_0.8.1.bb
index 1cbf2bd..3f12139 100644
--- a/meta-parsec/recipes-parsec/parsec-service/parsec-service_0.8.1.bb
+++ b/meta-parsec/recipes-parsec/parsec-service/parsec-service_0.8.1.bb
@@ -12,7 +12,12 @@ SRC_URI += "crate://crates.io/parsec-service/${PV} \
DEPENDS = "clang-native"
-PACKAGECONFIG ??= "TPM PKCS11 MBED-CRYPTO CRYPTOAUTHLIB"
+PACKAGECONFIG ??= "PKCS11 MBED-CRYPTO CRYPTOAUTHLIB"
+
+have_TPM = "${@bb.utils.contains('DISTRO_FEATURES', 'tpm2', 'TPM', '', d)}"
+PACKAGECONFIG:append = " ${@bb.utils.contains('BBFILE_COLLECTIONS',
'tpm-layer', '${have_TPM}', '', d)}"
+
+
PACKAGECONFIG[ALL] = "all-providers cryptoki/generate-bindings
tss-esapi/generate-bindings,,tpm2-tss libts,libts"
PACKAGECONFIG[TPM] = "tpm-provider tss-esapi/generate-bindings,,tpm2-tss"
PACKAGECONFIG[PKCS11] = "pkcs11-provider cryptoki/generate-bindings,"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56322): https://lists.yoctoproject.org/g/yocto/message/56322
Mute This Topic: https://lists.yoctoproject.org/mt/89453852/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
Hello Konrad,
Thank you very much!
The package is now building.
I have sent a corresponding patch.
Many greetings,
Matthias
-Ursprüngliche Nachricht-
Von: Konrad Weihmann
Gesendet: Montag, 28. Februar 2022 14:11
An: Matthias Klein ; yocto@lists.yoctoproject.org;
Tim Orling ; Richard Purdie
Betreff: Re: AW: AW: [yocto] python3-smbus no longer builds - Does anyone have
an idea?
Hi Matthias,
you're right :(
PYPA_WHEEL = "${S}/py-smbus/dist/smbus-*-*.whl"
finally does it
@Tim @Richard
PYPA_WHEEL doesn't respect SETUPTOOLS_SETUP_PATH, which might be another issue
to fix
BR
Konrad
On 28.02.22 14:04, Matthias Klein wrote:
> Hello Konrad,
>
> unfortunately it still does not build:
>
> ERROR: smbus-*-*.whl is not a valid wheel filename.
>
> Best regards,
> Matthias
>
> -Ursprüngliche Nachricht-
> Von: Konrad Weihmann
> Gesendet: Montag, 28. Februar 2022 13:59
> An: Matthias Klein ;
> yocto@lists.yoctoproject.org
> Betreff: Re: AW: [yocto] python3-smbus no longer builds - Does anyone have an
> idea?
>
> On 28.02.22 13:56, Matthias Klein wrote:
>> Hello Konrad,
>>
>> Thanks for the quick feedback.
>>
>> Have you been able to build the package with the change?
>> I get a similar error with it:
>
> Dang - that's the second issue being open in this series...
>
>>
>> ERROR: smbus-4.3-*.whl is not a valid wheel filename.
>
> Try
>
> PYPA_WHEEL = "${PIP_INSTALL_DIST_PATH}/smbus-*-*.whl"
>
> instead - and it should really work
>
>>
>> Best reagrds,
>> Matthias
>>
>> -Ursprüngliche Nachricht-
>> Von: Konrad Weihmann
>> Gesendet: Montag, 28. Februar 2022 13:51
>> An: Matthias Klein ;
>> yocto@lists.yoctoproject.org
>> Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an
>> idea?
>>
>> Hi Matthias,
>>
>> this is cause by merged PEP-517 changes.
>> To make it build again just inject
>>
>> PIP_INSTALL_PACKAGE = "smbus"
>>
>> into the recipe or a bbappend.
>> Mainly the python3-prefix of the recipe, makes the name guessing
>> fail, I suspect patches to be incoming soon
>>
>> BR
>> Konrad
>>
>> On 28.02.22 13:45, Matthias Klein wrote:
>>> Hello,
>>>
>>> the python3-smbus package no longer builds.
>>>
>>> The install step ends with the following error message:
>>>
>>> ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename.
>>>
>>> Does anyone have an idea what is the cause?
>>>
>>> Many greetings,
>>>
>>> Matthias
>>>
>>>
>>>
>>>
>>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56320): https://lists.yoctoproject.org/g/yocto/message/56320
Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper][hardknott 3/3] shared-repos: Use tar instead of rsync for speed
From: Richard Purdie
The rysnc of 20,000 files (650MB) onto the nas is slow taking ~3 minutes
at idle and worse at load. This is due to the number of files which
is a pain point for NFS. This piece of the build is also a bottleneck
since the rest of a build depends on it happening.
If we switch to zstd compressed tar, it takes 2.49s. Other compression
methods were much slower but zstd seems 'accptable' and speeds things
up too.
Signed-off-by: Richard Purdie
(cherry picked from commit aff49e938ee34e1fc5a2954e3e22a4ca1ae9ac7b)
Signed-off-by: Anuj Mittal
---
scripts/prepare-shared-repos | 4 ++--
scripts/send-qa-email| 6 --
scripts/shared-repo-unpack | 9 ++---
3 files changed, 12 insertions(+), 7 deletions(-)
diff --git a/scripts/prepare-shared-repos b/scripts/prepare-shared-repos
index c221e69..a5bc0da 100755
--- a/scripts/prepare-shared-repos
+++ b/scripts/prepare-shared-repos
@@ -39,5 +39,5 @@ with tempfile.TemporaryDirectory(prefix="shared-repo-temp-",
dir="/home/pokybuil
if args.publish_dir:
utils.publishrepo(tempdir, repo, args.publish_dir)
-utils.printheader("Running rsync")
-subprocess.check_call("rsync -a " + tempdir + "/* " + args.sharedsrcdir,
shell=True)
+utils.printheader("Creating shared src tarball")
+subprocess.check_call("tar -I zstd -cf " + args.sharedsrcdir.rstrip("/") +
".tar.zst ./*", shell=True, cwd=tempdir)
diff --git a/scripts/send-qa-email b/scripts/send-qa-email
index 1b69307..bc594df 100755
--- a/scripts/send-qa-email
+++ b/scripts/send-qa-email
@@ -45,9 +45,11 @@ buildtoolsdir = os.path.dirname(args.repojson) +
"/build/buildtools"
if os.path.exists(buildtoolsdir):
utils.enable_buildtools_tarball(buildtoolsdir)
+repodir = os.path.dirname(args.repojson) + "/build/repos"
+
if 'poky' in repos and os.path.exists(resulttool) and args.results_dir:
# Need the finalised revisions (not 'HEAD')
-targetrepodir = "%s/poky" % (args.sharedrepodir)
+targetrepodir = "%s/poky" % (repodir)
revision = subprocess.check_output(["git", "rev-parse", "HEAD"],
cwd=targetrepodir).decode('utf-8').strip()
branch = repos['poky']['branch']
repo = repos['poky']['url']
@@ -116,7 +118,7 @@ if args.send.lower() != 'true' or not args.publish_dir or
not args.release:
buildhashes = ""
for repo in sorted(repos.keys()):
# Need the finalised revisions (not 'HEAD')
-targetrepodir = "%s/%s" % (args.sharedrepodir, repo)
+targetrepodir = "%s/%s" % (repodir, repo)
revision = subprocess.check_output(["git", "rev-parse", "HEAD"],
cwd=targetrepodir).decode('utf-8').strip()
buildhashes += "%s: %s\n" % (repo, revision)
diff --git a/scripts/shared-repo-unpack b/scripts/shared-repo-unpack
index f08efa8..f7f87af 100755
--- a/scripts/shared-repo-unpack
+++ b/scripts/shared-repo-unpack
@@ -50,11 +50,14 @@ needrepos_baseddirs = [r.split('/')[0] for r in needrepos]
for repo in sorted(repos.keys()):
if repo not in needrepos_baseddirs:
continue
-targetrepodir = "%s/%s" % (targetsubdir, repo)
if args.cache_dir:
utils.printheader("Copying in repo %s" % repo)
-utils.mkdir(targetrepodir)
-subprocess.check_call(["rsync", "-a", "%s/%s" % (args.cache_dir,
repo), targetsubdir])
+utils.mkdir(targetsubdir)
+if args.target in ["a-full", "a-quick"]:
+# full/quick need all repo data due to send-qa-email
+subprocess.check_call(["tar", "-I", "zstd", "-C", targetsubdir,
"-xf", "%s.tar.zst" % args.cache_dir])
+else:
+subprocess.check_call(["tar", "-I", "zstd", "-C", targetsubdir,
"-xf", "%s.tar.zst" % args.cache_dir, "./" + repo])
else:
utils.printheader("Fetching repo %s" % repo)
utils.fetchgitrepo(targetsubdir, repo, repos[repo], stashdir)
--
2.35.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56319): https://lists.yoctoproject.org/g/yocto/message/56319
Mute This Topic: https://lists.yoctoproject.org/mt/89450921/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper][hardknott 2/3] prepare-shared-repos: Make it clear when rsync starts in logs
From: Richard Purdie
Signed-off-by: Richard Purdie
(cherry picked from commit 8e996a95a8902b40380dd477ecb606cc969cdee9)
Signed-off-by: Anuj Mittal
---
scripts/prepare-shared-repos | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/prepare-shared-repos b/scripts/prepare-shared-repos
index 1573f85..c221e69 100755
--- a/scripts/prepare-shared-repos
+++ b/scripts/prepare-shared-repos
@@ -39,4 +39,5 @@ with tempfile.TemporaryDirectory(prefix="shared-repo-temp-",
dir="/home/pokybuil
if args.publish_dir:
utils.publishrepo(tempdir, repo, args.publish_dir)
+utils.printheader("Running rsync")
subprocess.check_call("rsync -a " + tempdir + "/* " + args.sharedsrcdir,
shell=True)
--
2.35.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56318): https://lists.yoctoproject.org/g/yocto/message/56318
Mute This Topic: https://lists.yoctoproject.org/mt/89450919/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper][hardknott 1/3] scripts/prepare-shared-repos: Use tmpfs for speed
From: Richard Purdie
Signed-off-by: Richard Purdie
(cherry picked from commit 298a10575851d501204fe1ee0d1dcbcec37a66cd)
Signed-off-by: Anuj Mittal
---
scripts/prepare-shared-repos | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/prepare-shared-repos b/scripts/prepare-shared-repos
index 8400d09..1573f85 100755
--- a/scripts/prepare-shared-repos
+++ b/scripts/prepare-shared-repos
@@ -32,7 +32,7 @@ with open(args.repojson) as f:
stashdir = utils.getconfig("REPO_STASH_DIR", ourconfig)
-with tempfile.TemporaryDirectory(prefix="shared-repo-temp-", dir="/tmp") as
tempdir:
+with tempfile.TemporaryDirectory(prefix="shared-repo-temp-",
dir="/home/pokybuild/tmp") as tempdir:
for repo in sorted(repos.keys()):
utils.printheader("Intially fetching repo %s" % repo)
utils.fetchgitrepo(tempdir, repo, repos[repo], stashdir)
--
2.35.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56317): https://lists.yoctoproject.org/g/yocto/message/56317
Mute This Topic: https://lists.yoctoproject.org/mt/89450917/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
Hi Matthias,
you're right :(
PYPA_WHEEL = "${S}/py-smbus/dist/smbus-*-*.whl"
finally does it
@Tim @Richard
PYPA_WHEEL doesn't respect SETUPTOOLS_SETUP_PATH, which might be another
issue to fix
BR
Konrad
On 28.02.22 14:04, Matthias Klein wrote:
Hello Konrad,
unfortunately it still does not build:
ERROR: smbus-*-*.whl is not a valid wheel filename.
Best regards,
Matthias
-Ursprüngliche Nachricht-
Von: Konrad Weihmann
Gesendet: Montag, 28. Februar 2022 13:59
An: Matthias Klein ; yocto@lists.yoctoproject.org
Betreff: Re: AW: [yocto] python3-smbus no longer builds - Does anyone have an
idea?
On 28.02.22 13:56, Matthias Klein wrote:
Hello Konrad,
Thanks for the quick feedback.
Have you been able to build the package with the change?
I get a similar error with it:
Dang - that's the second issue being open in this series...
ERROR: smbus-4.3-*.whl is not a valid wheel filename.
Try
PYPA_WHEEL = "${PIP_INSTALL_DIST_PATH}/smbus-*-*.whl"
instead - and it should really work
Best reagrds,
Matthias
-Ursprüngliche Nachricht-
Von: Konrad Weihmann
Gesendet: Montag, 28. Februar 2022 13:51
An: Matthias Klein ; yocto@lists.yoctoproject.org
Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
Hi Matthias,
this is cause by merged PEP-517 changes.
To make it build again just inject
PIP_INSTALL_PACKAGE = "smbus"
into the recipe or a bbappend.
Mainly the python3-prefix of the recipe, makes the name guessing fail, I
suspect patches to be incoming soon
BR
Konrad
On 28.02.22 13:45, Matthias Klein wrote:
Hello,
the python3-smbus package no longer builds.
The install step ends with the following error message:
ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename.
Does anyone have an idea what is the cause?
Many greetings,
Matthias
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56316): https://lists.yoctoproject.org/g/yocto/message/56316
Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
Hello Konrad,
unfortunately it still does not build:
ERROR: smbus-*-*.whl is not a valid wheel filename.
Best regards,
Matthias
-Ursprüngliche Nachricht-
Von: Konrad Weihmann
Gesendet: Montag, 28. Februar 2022 13:59
An: Matthias Klein ; yocto@lists.yoctoproject.org
Betreff: Re: AW: [yocto] python3-smbus no longer builds - Does anyone have an
idea?
On 28.02.22 13:56, Matthias Klein wrote:
> Hello Konrad,
>
> Thanks for the quick feedback.
>
> Have you been able to build the package with the change?
> I get a similar error with it:
Dang - that's the second issue being open in this series...
>
> ERROR: smbus-4.3-*.whl is not a valid wheel filename.
Try
PYPA_WHEEL = "${PIP_INSTALL_DIST_PATH}/smbus-*-*.whl"
instead - and it should really work
>
> Best reagrds,
> Matthias
>
> -Ursprüngliche Nachricht-
> Von: Konrad Weihmann
> Gesendet: Montag, 28. Februar 2022 13:51
> An: Matthias Klein ; yocto@lists.yoctoproject.org
> Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an
> idea?
>
> Hi Matthias,
>
> this is cause by merged PEP-517 changes.
> To make it build again just inject
>
> PIP_INSTALL_PACKAGE = "smbus"
>
> into the recipe or a bbappend.
> Mainly the python3-prefix of the recipe, makes the name guessing fail, I
> suspect patches to be incoming soon
>
> BR
> Konrad
>
> On 28.02.22 13:45, Matthias Klein wrote:
>> Hello,
>>
>> the python3-smbus package no longer builds.
>>
>> The install step ends with the following error message:
>>
>> ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename.
>>
>> Does anyone have an idea what is the cause?
>>
>> Many greetings,
>>
>> Matthias
>>
>>
>>
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56315): https://lists.yoctoproject.org/g/yocto/message/56315
Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
ERROR: smbus-*-*.whl is not a valid wheel filename.
-Ursprüngliche Nachricht-
Von: Konrad Weihmann
Gesendet: Montag, 28. Februar 2022 13:59
An: Matthias Klein ; yocto@lists.yoctoproject.org
Betreff: Re: AW: [yocto] python3-smbus no longer builds - Does anyone have an
idea?
On 28.02.22 13:56, Matthias Klein wrote:
> Hello Konrad,
>
> Thanks for the quick feedback.
>
> Have you been able to build the package with the change?
> I get a similar error with it:
Dang - that's the second issue being open in this series...
>
> ERROR: smbus-4.3-*.whl is not a valid wheel filename.
Try
PYPA_WHEEL = "${PIP_INSTALL_DIST_PATH}/smbus-*-*.whl"
instead - and it should really work
>
> Best reagrds,
> Matthias
>
> -Ursprüngliche Nachricht-
> Von: Konrad Weihmann
> Gesendet: Montag, 28. Februar 2022 13:51
> An: Matthias Klein ; yocto@lists.yoctoproject.org
> Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an
> idea?
>
> Hi Matthias,
>
> this is cause by merged PEP-517 changes.
> To make it build again just inject
>
> PIP_INSTALL_PACKAGE = "smbus"
>
> into the recipe or a bbappend.
> Mainly the python3-prefix of the recipe, makes the name guessing fail, I
> suspect patches to be incoming soon
>
> BR
> Konrad
>
> On 28.02.22 13:45, Matthias Klein wrote:
>> Hello,
>>
>> the python3-smbus package no longer builds.
>>
>> The install step ends with the following error message:
>>
>> ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename.
>>
>> Does anyone have an idea what is the cause?
>>
>> Many greetings,
>>
>> Matthias
>>
>>
>>
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56314): https://lists.yoctoproject.org/g/yocto/message/56314
Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
On 28.02.22 13:56, Matthias Klein wrote:
Hello Konrad,
Thanks for the quick feedback.
Have you been able to build the package with the change?
I get a similar error with it:
Dang - that's the second issue being open in this series...
ERROR: smbus-4.3-*.whl is not a valid wheel filename.
Try
PYPA_WHEEL = "${PIP_INSTALL_DIST_PATH}/smbus-*-*.whl"
instead - and it should really work
Best reagrds,
Matthias
-Ursprüngliche Nachricht-
Von: Konrad Weihmann
Gesendet: Montag, 28. Februar 2022 13:51
An: Matthias Klein ; yocto@lists.yoctoproject.org
Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
Hi Matthias,
this is cause by merged PEP-517 changes.
To make it build again just inject
PIP_INSTALL_PACKAGE = "smbus"
into the recipe or a bbappend.
Mainly the python3-prefix of the recipe, makes the name guessing fail, I
suspect patches to be incoming soon
BR
Konrad
On 28.02.22 13:45, Matthias Klein wrote:
Hello,
the python3-smbus package no longer builds.
The install step ends with the following error message:
ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename.
Does anyone have an idea what is the cause?
Many greetings,
Matthias
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56313): https://lists.yoctoproject.org/g/yocto/message/56313
Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
Hello Konrad, Thanks for the quick feedback. Have you been able to build the package with the change? I get a similar error with it: ERROR: smbus-4.3-*.whl is not a valid wheel filename. Best reagrds, Matthias -Ursprüngliche Nachricht- Von: Konrad Weihmann Gesendet: Montag, 28. Februar 2022 13:51 An: Matthias Klein ; yocto@lists.yoctoproject.org Betreff: Re: [yocto] python3-smbus no longer builds - Does anyone have an idea? Hi Matthias, this is cause by merged PEP-517 changes. To make it build again just inject PIP_INSTALL_PACKAGE = "smbus" into the recipe or a bbappend. Mainly the python3-prefix of the recipe, makes the name guessing fail, I suspect patches to be incoming soon BR Konrad On 28.02.22 13:45, Matthias Klein wrote: > Hello, > > the python3-smbus package no longer builds. > > The install step ends with the following error message: > > ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename. > > Does anyone have an idea what is the cause? > > Many greetings, > > Matthias > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56312): https://lists.yoctoproject.org/g/yocto/message/56312 Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] python3-smbus no longer builds - Does anyone have an idea?
Hi Matthias, this is cause by merged PEP-517 changes. To make it build again just inject PIP_INSTALL_PACKAGE = "smbus" into the recipe or a bbappend. Mainly the python3-prefix of the recipe, makes the name guessing fail, I suspect patches to be incoming soon BR Konrad On 28.02.22 13:45, Matthias Klein wrote: Hello, the python3-smbus package no longer builds. The install step ends with the following error message: ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename. Does anyone have an idea what is the cause? Many greetings, Matthias -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56311): https://lists.yoctoproject.org/g/yocto/message/56311 Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] python3-smbus no longer builds - Does anyone have an idea?
Hello, the python3-smbus package no longer builds. The install step ends with the following error message: ERROR: python3_smbus-4.3-*.whl is not a valid wheel filename. Does anyone have an idea what is the cause? Many greetings, Matthias -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56310): https://lists.yoctoproject.org/g/yocto/message/56310 Mute This Topic: https://lists.yoctoproject.org/mt/89449220/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Correspondance between Qt5 components and meta-qt5 recipes
Hi Perceval, Just a rough guess, I think you want qtsvg in DEPENDS for svg support and/or qtbase in DEPENDS for gif support. I don't know of any mapping but the recipes seem to align quite clearly with the components. And I think you can ignore setting RDEPENDS manually. Typically the RDEPENDS do not need to be done manually and it is handled auto-magically [1]. When the packaging is done, the task scans the elf headers to find what libraries are depended on. i.e. It'll see if your app depends on the qtsvg lib. From there, it determines automatically which package provides that lib and adds it to the rdeps of the package data. Adding to RDEPENDS manually is normally only needed if you have something the scanner cannot pick up on automatically. (eg. shell scripts that have dependencies, dynamically injected libs, etc). Been awhile since I did anything with qt5, pretty sure the libs are linked in a normal sense that the scanner will detect the rdepends automatically. [1] https://www.yoctoproject.org/docs/3.1/overview-manual/overview-manual.html#automatically-added-runtime-dependencies Kind regards, Michael On Sun, Feb 27, 2022 at 3:38 PM Perceval wrote: > Hello everyone, > > I don't know if it is the right place or if my question belong more in the > >- openembedded-architecture mailing list. > > > > I'm trying to build an image with my Qt5 based application. I know which > Qt5 component I need to build and to run my application but I'm struggeling > to understand what are the corresponding recipes to put in DEPENDS and > RDEPENDS according to the components I use. > > For example: if I want to build a graphical application with image display > support I would need (if I understand correctly): > for svg support: qtsvg in RDEPENDS > but for gif support: qtbase in DEPENDS with PACKAGECONFIG_append = "gif" > in a qtbase_%.bbappend > It is a little bit confusing for me. > > My question is: > Is there any documentation or table mapping Qt5 components or libraries > and the corresponding recipe in the meta-Qt5 layer (with the correct > PACKAGEGROUP to set if needed)? > > Thank you very much, > Have a great day, > > -- > *Perceval ARENOU* > Embedded Software Engineer > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56309): https://lists.yoctoproject.org/g/yocto/message/56309 Mute This Topic: https://lists.yoctoproject.org/mt/89429215/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] extract several source tree with devtool
You probably need to fix devtool as it is not designed to handle this, patches welcome. Alex On Mon, 28 Feb 2022 at 09:11, Julien STEPHAN wrote: > > Hi all, > > Any ideas? > > Thanks > Julien > > Le lun. 21 févr. 2022 à 18:24, Julien STEPHAN via lists.yoctoproject.org > a écrit : >> >> Hi all, >> >> I am wondering if it is possible to extract both a git repo and a tarball >> using devtool modify? >> Example: >> I am trying to use devtool modify on tensorflow-lite recipe >> (https://git.yoctoproject.org/meta-tensorflow/tree/recipes-framework/tensorflow/tensorflow_2.6.1.bb). >> The `tensorflow.inc` file fetches the tensorflow repository using git, then >> `tensorflow_2.6.1.bb` fetches 2 tarballs. The tarballs are extracted inside >> WORKDIR then files are installed inside the do_install() function. This is >> running correctly using `bitbake tensorflow`. When using `devtool modify >> tensorflow`, the tarballs are not extracted, then I get an error at the >> do_install stage: files from tarball don't exist. >> >> This is a general question not related to tensorflow. Any suggestions on how >> to handle this? Either on the recipe side or on the devtool side? >> Best >> Julien >> >> >> > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56308): https://lists.yoctoproject.org/g/yocto/message/56308 Mute This Topic: https://lists.yoctoproject.org/mt/89298811/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] extract several source tree with devtool
Hi all, Any ideas? Thanks Julien Le lun. 21 févr. 2022 à 18:24, Julien STEPHAN via lists.yoctoproject.org a écrit : > Hi all, > > I am wondering if it is possible to extract both a git repo and a tarball > using devtool modify? > Example: > I am trying to use devtool modify on tensorflow-lite recipe ( > https://git.yoctoproject.org/meta-tensorflow/tree/recipes-framework/tensorflow/tensorflow_2.6.1.bb). > The `tensorflow.inc` file fetches the tensorflow repository using git, then > `tensorflow_2.6.1.bb` fetches 2 tarballs. The tarballs are extracted > inside WORKDIR then files are installed inside the do_install() function. > This is running correctly using `bitbake tensorflow`. When using `devtool > modify tensorflow`, the tarballs are not extracted, then I get an error at > the do_install stage: files from tarball don't exist. > > This is a general question not related to tensorflow. Any suggestions on > how to handle this? Either on the recipe side or on the devtool side? > Best > Julien > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56307): https://lists.yoctoproject.org/g/yocto/message/56307 Mute This Topic: https://lists.yoctoproject.org/mt/89298811/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
