Date   

[meta-oe][PATCH 3/5] fontforge: Inherit python3targetconfig

Khem Raj
 

It currently ends up using native python3-config which adds native paths
to compiler includes which is not what we want.

Signed-off-by: Khem Raj <raj.khem@...>
---
meta-oe/recipes-graphics/fontforge/fontforge_20220308.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-oe/recipes-graphics/fontforge/fontforge_20220308.bb b/meta-oe/recipes-graphics/fontforge/fontforge_20220308.bb
index c53f2db01b..ddb4443baa 100644
--- a/meta-oe/recipes-graphics/fontforge/fontforge_20220308.bb
+++ b/meta-oe/recipes-graphics/fontforge/fontforge_20220308.bb
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = " \
DEPENDS = "python3 glib-2.0 pango giflib tiff libxml2 jpeg libtool uthash gettext-native libspiro"
DEPENDS:append:class-target = " libxi"

-inherit cmake pkgconfig python3native features_check gettext gtk-icon-cache mime mime-xdg
+inherit cmake pkgconfig python3native python3targetconfig features_check gettext gtk-icon-cache mime mime-xdg

REQUIRED_DISTRO_FEATURES:append:class-target = " x11"

--
2.38.1


[meta-oe][PATCH 2/5] surf: Depend on gcr-3

Khem Raj
 

It has been renamed in oe-core

Signed-off-by: Khem Raj <raj.khem@...>
---
meta-oe/recipes-graphics/surf/surf_2.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-oe/recipes-graphics/surf/surf_2.1.bb b/meta-oe/recipes-graphics/surf/surf_2.1.bb
index 45ae79305a..1f55848a79 100644
--- a/meta-oe/recipes-graphics/surf/surf_2.1.bb
+++ b/meta-oe/recipes-graphics/surf/surf_2.1.bb
@@ -5,7 +5,7 @@ SECTION = "x11/graphics"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=2a6f86d002ae9ae1eb1ccc466289f146"

-DEPENDS = "webkitgtk gtk+3 glib-2.0 gcr"
+DEPENDS = "webkitgtk gtk+3 glib-2.0 gcr-3"

REQUIRED_DISTRO_FEATURES = "x11 opengl"

--
2.38.1


[meta-gnome][PATCH 1/5] amtk: Add missing dep on python3-pygments-native

Khem Raj
 

Fixes
File "TOPDIR/build/tmp/work/mips32r2-yoe-linux/amtk/5.6.1-r0/recipe-sysroot-native/usr/share/gtk-doc/python/gtkdoc/highlight.py", line 27, in <module>
from pygments import highlight
ModuleNotFoundError: No module named 'pygments'

Signed-off-by: Khem Raj <raj.khem@...>
---
meta-gnome/recipes-gnome/amtk/amtk_5.6.1.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta-gnome/recipes-gnome/amtk/amtk_5.6.1.bb b/meta-gnome/recipes-gnome/amtk/amtk_5.6.1.bb
index 8cb2fa79b5..fbc8f38454 100644
--- a/meta-gnome/recipes-gnome/amtk/amtk_5.6.1.bb
+++ b/meta-gnome/recipes-gnome/amtk/amtk_5.6.1.bb
@@ -8,6 +8,7 @@ DEPENDS = " \
gtk-doc-native \
libxslt-native \
docbook-xsl-stylesheets-native \
+ python3-pygments-native \
"

GNOMEBASEBUILDCLASS = "meson"
--
2.38.1


Re: [meta-python][PATCH V3 1/2] python3-binwalk: add recipe for version 2.3.3

Khem Raj
 

Can you rebase these patches on top of master or master-next and
resend v3 please ?

On Thu, Dec 1, 2022 at 12:35 AM tomzy <tomasz.zyjewski@...> wrote:

Install binwalk utility.

Binwalk is a fast, easy to use tool for analyzing, reverse engineering,
and extracting firmware images.

Signed-off-by: Tomasz Żyjewski <tomasz.zyjewski@...>
---
.../python/python3-binwalk_2.3.3.bb | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 meta-python/recipes-devtools/python/python3-binwalk_2.3.3.bb

diff --git a/meta-python/recipes-devtools/python/python3-binwalk_2.3.3.bb b/meta-python/recipes-devtools/python/python3-binwalk_2.3.3.bb
new file mode 100644
index 000000000000..362efa275148
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python3-binwalk_2.3.3.bb
@@ -0,0 +1,17 @@
+SUMMARY = "Firmware analysis tool"
+DESCRIPTION = "This package contains Python Binwalk tool. Binwalk is a fast, \
+easy to use tool for analyzing, reverse engineering, and extracting firmware \
+images."
+HOMEPAGE = "https://github.com/ReFirmLabs/binwalk"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=65bbee055d3ea3bfc475f07aecf4de64"
+
+SRC_URI = "git://github.com/ReFirmLabs/binwalk;protocol=https;branch=master"
+
+SRCREV = "fa0c0bd59b8588814756942fe4cb5452e76c1dcd"
+
+S = "${WORKDIR}/git"
+
+inherit setuptools3
+
+RDEPENDS:${PN} += "python3-core"
--
2.25.1




[meta-oe][PATCH] perfetto: update 27.1 -> 28.0

Markus Volk
 

Signed-off-by: Markus Volk <f_l_k@...>
---
.../files/0001-meson-add-pc-file-for-lib_perfetto.patch | 2 +-
meta-oe/recipes-devtools/perfetto/perfetto.inc | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-oe/recipes-devtools/perfetto/files/0001-meson-add-pc-fi=
le-for-lib_perfetto.patch b/meta-oe/recipes-devtools/perfetto/files/0001-=
meson-add-pc-file-for-lib_perfetto.patch
index 70de44173..d6092afeb 100644
--- a/meta-oe/recipes-devtools/perfetto/files/0001-meson-add-pc-file-for-=
lib_perfetto.patch
+++ b/meta-oe/recipes-devtools/perfetto/files/0001-meson-add-pc-file-for-=
lib_perfetto.patch
@@ -17,7 +17,7 @@ index 06015141c..752b4d928 100644
['c','cpp'],
- default_options: ['c_std=3Dc99', 'cpp_std=3Dc++11']
+ default_options: ['c_std=3Dc99', 'cpp_std=3Dc++11'],
-+ version: '27.1'
++ version: '28.0'
)
=20
+soversion =3D meson.project_version()
diff --git a/meta-oe/recipes-devtools/perfetto/perfetto.inc b/meta-oe/rec=
ipes-devtools/perfetto/perfetto.inc
index 5cb6f8bb3..a8e72af1a 100644
--- a/meta-oe/recipes-devtools/perfetto/perfetto.inc
+++ b/meta-oe/recipes-devtools/perfetto/perfetto.inc
@@ -3,7 +3,7 @@ HOMEPAGE =3D "https://github.com/google/perfetto"
=20
SRC_URI =3D "git://github.com/google/perfetto.git;protocol=3Dhttps;name=3D=
perfetto;nobranch=3D1"
=20
-SRCREV_perfetto =3D "1c52b5e132312aeb007ed180d4ba1d8d66227923"
-PV =3D "27.1"
+SRCREV_perfetto =3D "99ead408d98eaa25b7819c7e059734bea42fa148"
+PV =3D "28.0"
=20
S =3D "${WORKDIR}/git"
--=20
2.34.1


Re: [meta-gnome][PATCH 0/3] gvfs: use native ssh client

Mikko Rapeli
 

Hi,

On Thu, Dec 01, 2022 at 08:20:44AM -0600, Alex Stewart wrote:
Hey Mikko,

On 12/1/22 07:57, Mikko Rapeli wrote:
Hi,

On Thu, Dec 01, 2022 at 07:41:45AM -0600, Alex Stewart wrote:
While rebasing the NI LinuxRT distro to kirkstone, I noticed that my
pyrex container fails gvfs:do_configure with a meson error about not
finding an `ssh` client.

| Program ssh found: NO
|
| ../gvfs-1.50.0/meson.build:462:2: ERROR: Assert failed: SFTP backend requested but a ssh client is required


After some investigation, it seems that gvfs is configured to use the
`ssh` client implementation in the build machine's PATH. If no native
implementation is provided in the native sysroot, it will default to
using the host machine's implementation.

My new kirkstone pyrex container happened to not install an ssh client,
and so would fail. Since ssh isn't a requirement to run BB or OE, I
don't think it's appropriate to use the host's ssh.


This patchset adds the native bbclass to openssh, when the user includes
meta-oe in his layerstack, and then provides the openssh-native content
to gvfs through its DEPENDS. This is sufficient to resolve the error on
my kirkstone pyrex container.

NOTE: It's a little odd to me that the OE-core openssh recipe doesn't
already inherit native.bbclass - when it *does* inherit
nativesdk.bbclass. I would be open to moving the openssh changes in this
PR to OE-core directly, if someone can ACK that it would be more
appropriate to do so.
Why would one really need to build native, the compiler host machine,
version of openssh? Why even gvfs is needed for native?!
For target or nativesdk the needs are clear, but for native?
I'm not sure I understand the question. Are you asking why the gvfs compile
requires an ssh client in the build host toolchain?
What requires gvfs for native build target? I think that dependency
should be removed. I don't think this dependency makes sense and I don't
think it will really be used by anything.

If there is a real use case, then you could try to remove the ssh
dependency. You likely don't need ssh communication at build time so
just disable the feature completely.

Cheers,

-Mikko


Re: [meta-gnome][PATCH 3/3] gvfs: use native ssh client

Alex Stewart
 

On 12/1/22 07:59, Mikko Rapeli wrote:
Hi,

On Thu, Dec 01, 2022 at 07:41:48AM -0600, Alex Stewart wrote:
When the `sftp` option is enabled in gvfs, meson tries to find a valid
`ssh` binary in the build host's PATH during do_configure. If a -native
implementation is not found, meson will try to satisfy the binary using
the build machine's hosttools directly - which is generally undesirable.

DEPEND on openssh-native, so that an ssh client implementation is always
in the PATH during configuration.
This sounds wrong. Why doesn't meson look into the sysroot and add the
dependency to target "openssh" (or "virtual/ssh-client")?

If the path to the binary will be hard coded, then that needs to be
fixed to be the path in expected target system rootfs.
I guessed it might have something to do with `ssh` not being defined within this `meson.cross` binaries list (or maybe the .native version) [1]. I tried adding it, along with a DEPENDS on openssh, but that didn't seem to work either.

I'm not very familiar with meson configurations. If you have some guidance on a better design, I'd be happy to give it a shot.

[1] https://git.openembedded.org/openembedded-core/tree/meta/classes-recipe/meson.bbclass#n65


Cheers,

-Mikko

Signed-off-by: Alex Stewart <alex.stewart@...>
---
meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb b/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
index 4c251d2f4..9e29afd48 100644
--- a/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
+++ b/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
@@ -12,6 +12,7 @@ DEPENDS += "\
gsettings-desktop-schemas \
libgudev \
libsecret \
+ openssh-native \
shadow-native \
"
--
2.38.1
--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)

alex.stewart@...


Re: [meta-gnome][PATCH 0/3] gvfs: use native ssh client

Alex Stewart
 

Hey Mikko,

On 12/1/22 07:57, Mikko Rapeli wrote:
Hi,

On Thu, Dec 01, 2022 at 07:41:45AM -0600, Alex Stewart wrote:
While rebasing the NI LinuxRT distro to kirkstone, I noticed that my
pyrex container fails gvfs:do_configure with a meson error about not
finding an `ssh` client.

| Program ssh found: NO
|
| ../gvfs-1.50.0/meson.build:462:2: ERROR: Assert failed: SFTP backend requested but a ssh client is required


After some investigation, it seems that gvfs is configured to use the
`ssh` client implementation in the build machine's PATH. If no native
implementation is provided in the native sysroot, it will default to
using the host machine's implementation.

My new kirkstone pyrex container happened to not install an ssh client,
and so would fail. Since ssh isn't a requirement to run BB or OE, I
don't think it's appropriate to use the host's ssh.


This patchset adds the native bbclass to openssh, when the user includes
meta-oe in his layerstack, and then provides the openssh-native content
to gvfs through its DEPENDS. This is sufficient to resolve the error on
my kirkstone pyrex container.

NOTE: It's a little odd to me that the OE-core openssh recipe doesn't
already inherit native.bbclass - when it *does* inherit
nativesdk.bbclass. I would be open to moving the openssh changes in this
PR to OE-core directly, if someone can ACK that it would be more
appropriate to do so.
Why would one really need to build native, the compiler host machine,
version of openssh? Why even gvfs is needed for native?!
For target or nativesdk the needs are clear, but for native?
I'm not sure I understand the question. Are you asking why the gvfs compile requires an ssh client in the build host toolchain?

If so, I don't know the answer. Trolling through the history of the gvfs project didn't provide me with very much context as to why it is required. And I didn't see an obvious way to work-around the requirement.

These kind of things really need good justifications or the whole host
tooling graph explodes and build times with it. In most cases the native
host target has a lot less build dependencies and features enabled
because of this reason.
Agreed. I'd love to eschew this requirement; but that is probably a conversation with gvfs upstream about why it exists in the first place.

--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)

alex.stewart@...


Re: [meta-gnome][PATCH 3/3] gvfs: use native ssh client

Mikko Rapeli
 

Hi,

On Thu, Dec 01, 2022 at 07:41:48AM -0600, Alex Stewart wrote:
When the `sftp` option is enabled in gvfs, meson tries to find a valid
`ssh` binary in the build host's PATH during do_configure. If a -native
implementation is not found, meson will try to satisfy the binary using
the build machine's hosttools directly - which is generally undesirable.

DEPEND on openssh-native, so that an ssh client implementation is always
in the PATH during configuration.
This sounds wrong. Why doesn't meson look into the sysroot and add the
dependency to target "openssh" (or "virtual/ssh-client")?

If the path to the binary will be hard coded, then that needs to be
fixed to be the path in expected target system rootfs.

Cheers,

-Mikko

Signed-off-by: Alex Stewart <alex.stewart@...>
---
meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb b/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
index 4c251d2f4..9e29afd48 100644
--- a/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
+++ b/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
@@ -12,6 +12,7 @@ DEPENDS += "\
gsettings-desktop-schemas \
libgudev \
libsecret \
+ openssh-native \
shadow-native \
"

--
2.38.1



Re: [meta-gnome][PATCH 0/3] gvfs: use native ssh client

Mikko Rapeli
 

Hi,

On Thu, Dec 01, 2022 at 07:41:45AM -0600, Alex Stewart wrote:
While rebasing the NI LinuxRT distro to kirkstone, I noticed that my
pyrex container fails gvfs:do_configure with a meson error about not
finding an `ssh` client.

| Program ssh found: NO
|
| ../gvfs-1.50.0/meson.build:462:2: ERROR: Assert failed: SFTP backend requested but a ssh client is required


After some investigation, it seems that gvfs is configured to use the
`ssh` client implementation in the build machine's PATH. If no native
implementation is provided in the native sysroot, it will default to
using the host machine's implementation.

My new kirkstone pyrex container happened to not install an ssh client,
and so would fail. Since ssh isn't a requirement to run BB or OE, I
don't think it's appropriate to use the host's ssh.


This patchset adds the native bbclass to openssh, when the user includes
meta-oe in his layerstack, and then provides the openssh-native content
to gvfs through its DEPENDS. This is sufficient to resolve the error on
my kirkstone pyrex container.

NOTE: It's a little odd to me that the OE-core openssh recipe doesn't
already inherit native.bbclass - when it *does* inherit
nativesdk.bbclass. I would be open to moving the openssh changes in this
PR to OE-core directly, if someone can ACK that it would be more
appropriate to do so.
Why would one really need to build native, the compiler host machine,
version of openssh? Why even gvfs is needed for native?!
For target or nativesdk the needs are clear, but for native?

These kind of things really need good justifications or the whole host
tooling graph explodes and build times with it. In most cases the native
host target has a lot less build dependencies and features enabled
because of this reason.

Cheers,

-Mikko


OEDvM and OpenEmbedded Workshop

Josef Holzmayr
 

Hello fellow OpenEmbeddeders!

Less than 24 hours until we kick off the OpenEmbedded Developers virtual Meeting 2022.11! For more details, please see https://www.openembedded.org/wiki/OEDvM_2022.11

You can join us directly via https://zoom.us/j/99151508871

Also we have great news: adjacent to FOSDEM, a workshop will take place in Brussels on February 6th. Be sure to check it out at https://pretalx.com/openembedded-workshop-2023/ and submit your ideas via https://pretalx.com/openembedded-workshop-2023/cfp

See you real soon!
Josef on behalf of the OE board


[meta-gnome][PATCH 3/3] gvfs: use native ssh client

Alex Stewart
 

When the `sftp` option is enabled in gvfs, meson tries to find a valid
`ssh` binary in the build host's PATH during do_configure. If a -native
implementation is not found, meson will try to satisfy the binary using
the build machine's hosttools directly - which is generally undesirable.

DEPEND on openssh-native, so that an ssh client implementation is always
in the PATH during configuration.

Signed-off-by: Alex Stewart <alex.stewart@...>
---
meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb b/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
index 4c251d2f4..9e29afd48 100644
--- a/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
+++ b/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
@@ -12,6 +12,7 @@ DEPENDS += "\
gsettings-desktop-schemas \
libgudev \
libsecret \
+ openssh-native \
shadow-native \
"

--
2.38.1


[meta-gnome][PATCH 2/3] gvfs: stylize DEPENDS

Alex Stewart
 

Use multiline styling in the gvfs DEPENDS variable assignment, so that
diffs are easier to understand.

Also alpha-sort the DEPENDS, since their order isn't meaningful.

Signed-off-by: Alex Stewart <alex.stewart@...>
---
meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb b/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
index e8d9f16de..4c251d2f4 100644
--- a/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
+++ b/meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb
@@ -5,8 +5,15 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=05df38dd77c35ec8431f212410a3329e"
GNOMEBASEBUILDCLASS = "meson"
inherit gnomebase gsettings bash-completion gettext upstream-version-is-even features_check useradd

-DEPENDS += "libsecret glib-2.0 glib-2.0-native libgudev shadow-native \
- gsettings-desktop-schemas dbus"
+DEPENDS += "\
+ dbus \
+ glib-2.0 \
+ glib-2.0-native \
+ gsettings-desktop-schemas \
+ libgudev \
+ libsecret \
+ shadow-native \
+"

RDEPENDS:${PN} += "gsettings-desktop-schemas"

--
2.38.1


[meta-gnome][PATCH 1/3] openssh: add native BBCLASSEXTEND

Alex Stewart
 

A native `ssh` client binary is needed when compiling `gvfs` with the
`sftp` option enabled.

Add the native bbclass to openssh, so that openssh-native can be used by
gvfs.

Signed-off-by: Alex Stewart <alex.stewart@...>
---
meta-gnome/recipes-connectivity/openssh/openssh_%.bbappend | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 meta-gnome/recipes-connectivity/openssh/openssh_%.bbappend

diff --git a/meta-gnome/recipes-connectivity/openssh/openssh_%.bbappend b/meta-gnome/recipes-connectivity/openssh/openssh_%.bbappend
new file mode 100644
index 000000000..25dcaa270
--- /dev/null
+++ b/meta-gnome/recipes-connectivity/openssh/openssh_%.bbappend
@@ -0,0 +1,2 @@
+# An ssh native client binary is needed by the gvfs do_configure.
+BBCLASSEXTEND += "native"
--
2.38.1


[meta-gnome][PATCH 0/3] gvfs: use native ssh client

Alex Stewart
 

While rebasing the NI LinuxRT distro to kirkstone, I noticed that my
pyrex container fails gvfs:do_configure with a meson error about not
finding an `ssh` client.

| Program ssh found: NO
|
| ../gvfs-1.50.0/meson.build:462:2: ERROR: Assert failed: SFTP backend requested but a ssh client is required


After some investigation, it seems that gvfs is configured to use the
`ssh` client implementation in the build machine's PATH. If no native
implementation is provided in the native sysroot, it will default to
using the host machine's implementation.

My new kirkstone pyrex container happened to not install an ssh client,
and so would fail. Since ssh isn't a requirement to run BB or OE, I
don't think it's appropriate to use the host's ssh.


This patchset adds the native bbclass to openssh, when the user includes
meta-oe in his layerstack, and then provides the openssh-native content
to gvfs through its DEPENDS. This is sufficient to resolve the error on
my kirkstone pyrex container.


NOTE: It's a little odd to me that the OE-core openssh recipe doesn't
already inherit native.bbclass - when it *does* inherit
nativesdk.bbclass. I would be open to moving the openssh changes in this
PR to OE-core directly, if someone can ACK that it would be more
appropriate to do so.

Alex Stewart (3):
openssh: add native BBCLASSEXTEND
gvfs: stylize DEPENDS
gvfs: use native ssh client

.../recipes-connectivity/openssh/openssh_%.bbappend | 2 ++
meta-gnome/recipes-gnome/gvfs/gvfs_1.50.2.bb | 12 ++++++++++--
2 files changed, 12 insertions(+), 2 deletions(-)
create mode 100644 meta-gnome/recipes-connectivity/openssh/openssh_%.bbappend

--
2.38.1


Re: [meta-python][PATCH 2/2] python3-uefi-firmware: add recipe for version 1.9

tomzy
 

On Wed, Nov 30, 2022 at 09:08 PM, Khem Raj wrote:
On 11/29/22 11:29 PM, tomzy wrote:
On Fri, Nov 25, 2022 at 3:44 AM tomzy <tomasz.zyjewski@...
<mailto:tomasz.zyjewski@...>> wrote:

Install uefi-firmware-parser tool

Signed-off-by: Tomasz Żyjewski <tomasz.zyjewski@...
<mailto:tomasz.zyjewski@...>>
---
 .../python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>         | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644
meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>

diff --git
a/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>
b/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>
new file mode 100644
index 000000000000..ba3124b36e60
--- /dev/null
+++
b/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>
@@ -0,0 +1,17 @@
+SUMMARY = "Various data structures and parsing tools for UEFI
firmware."
+DESCRIPTION = "This package contains Python UEFI firmware parser
tool. The \
+UEFI firmware parser is a simple module and set of scripts for
parsing, \
+extracting, and recreating UEFI firmware volumes. This includes
parsing \
+modules for BIOS, OptionROM, Intel ME and other formats too."
+HOMEPAGE = "https://github.com/theopolis/uefi-firmware-parser
<https://github.com/theopolis/uefi-firmware-parser>"
+AUTHOR = "Teddy Reed <teddy@... <mailto:teddy@...>>"
+LICENSE = "BSD-2-Clause & BSD-3-Clause"
+LIC_FILES_CHKSUM =
"file://setup.py;md5=90fa5bae1547550f1c1993f651eda955"
+
+SRC_URI =
"https://files.pythonhosted.org/packages/7e/b4/a4ec646d24a1aad709fdb83de6e5eddd6cb24faec02f3a94a3af3b0aba28/uefi_firmware-${PV}.tar.gz <https://files.pythonhosted.org/packages/7e/b4/a4ec646d24a1aad709fdb83de6e5eddd6cb24faec02f3a94a3af3b0aba28/uefi_firmware-$%7BPV%7D.tar.gz>"

If you’re fetching from  pythonhosted, you could very likely
simplify the recipe by inheriting pypi bbclass

+SRC_URI[md5sum] = "ee5011b4d0bcb0eb7c06295e0107894f"

These days, we only really use the sha256sum
+SRC_URI[sha256sum] =
"234119dd92780c67cce3b664e86119c41d0b2af188d7f372b69789b32c5d5cd0" +
+S = "${WORKDIR}/uefi_firmware-${PV}" + +inherit setuptools3 -- 2.25.1


Used git fetcher here, I just send PATCH V2, not sure if it visible on
mailing list.
Its not. Where did you send it ?

I must had something wrong with my email settings. Now it is sent. Just pushed V3 because of typo in subject-prefix.

uefi-firmware: https://lists.openembedded.org/g/openembedded-devel/message/99883

binwalk: https://lists.openembedded.org/g/openembedded-devel/message/99882


[meta-python][PATCH V3 2/2] python3-uefi-firmware: add recipe for version 1.9

tomzy
 

Install uefi-firmware-parser tool

The UEFI firmware parseer is a simple module and set of scripts for
parsing, extracting, and recreating UEFI firmware volumes.

Signed-off-by: Tomasz Żyjewski <tomasz.zyjewski@...>
---
.../python/python3-uefi-firmware_1.9.bb | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb

diff --git a/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb b/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
new file mode 100644
index 000000000000..3837a17437b1
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
@@ -0,0 +1,17 @@
+SUMMARY = "Various data structures and parsing tools for UEFI firmware."
+DESCRIPTION = "This package contains Python UEFI firmware parser tool. The \
+UEFI firmware parser is a simple module and set of scripts for parsing, \
+extracting, and recreating UEFI firmware volumes. This includes parsing \
+modules for BIOS, OptionROM, Intel ME and other formats too."
+HOMEPAGE = "https://github.com/theopolis/uefi-firmware-parser"
+AUTHOR = "Teddy Reed <teddy@...>"
+LICENSE = "BSD-2-Clause & BSD-3-Clause"
+LIC_FILES_CHKSUM = "file://setup.py;md5=90fa5bae1547550f1c1993f651eda955"
+
+SRC_URI = "git://github.com/theopolis/uefi-firmware-parser;protocol=https;branch=master"
+
+SRCREV = "502f1bada1ed11fdd1792646fda0bfafb8fa57fb"
+
+S = "${WORKDIR}/git"
+
+inherit setuptools3
--
2.25.1


[meta-python][PATCH V3 1/2] python3-binwalk: add recipe for version 2.3.3

tomzy
 

Install binwalk utility.

Binwalk is a fast, easy to use tool for analyzing, reverse engineering,
and extracting firmware images.

Signed-off-by: Tomasz Żyjewski <tomasz.zyjewski@...>
---
.../python/python3-binwalk_2.3.3.bb | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 meta-python/recipes-devtools/python/python3-binwalk_2.3.3.bb

diff --git a/meta-python/recipes-devtools/python/python3-binwalk_2.3.3.bb b/meta-python/recipes-devtools/python/python3-binwalk_2.3.3.bb
new file mode 100644
index 000000000000..362efa275148
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python3-binwalk_2.3.3.bb
@@ -0,0 +1,17 @@
+SUMMARY = "Firmware analysis tool"
+DESCRIPTION = "This package contains Python Binwalk tool. Binwalk is a fast, \
+easy to use tool for analyzing, reverse engineering, and extracting firmware \
+images."
+HOMEPAGE = "https://github.com/ReFirmLabs/binwalk"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=65bbee055d3ea3bfc475f07aecf4de64"
+
+SRC_URI = "git://github.com/ReFirmLabs/binwalk;protocol=https;branch=master"
+
+SRCREV = "fa0c0bd59b8588814756942fe4cb5452e76c1dcd"
+
+S = "${WORKDIR}/git"
+
+inherit setuptools3
+
+RDEPENDS:${PN} += "python3-core"
--
2.25.1


[meta-networking][PATCH] waf-samba.bbclass: point PYTHON_CONFIG to target python3-config

Khem Raj
 

Ensures that waf detects and uses it correctly

Signed-off-by: Khem Raj <raj.khem@...>
---
meta-networking/classes/waf-samba.bbclass | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta-networking/classes/waf-samba.bbclass b/meta-networking/classes/waf-samba.bbclass
index 9c32952f6a..41909788f7 100644
--- a/meta-networking/classes/waf-samba.bbclass
+++ b/meta-networking/classes/waf-samba.bbclass
@@ -95,6 +95,7 @@ do_configure() {
export STAGING_LIBDIR=${STAGING_LIBDIR}
export STAGING_INCDIR=${STAGING_INCDIR}
export PYTHONPATH=${STAGING_DIR_HOST}${PYTHON_SITEPACKAGES_DIR}
+ export PYTHON_CONFIG=${STAGING_EXECPREFIXDIR}/python-target-config/python3-config

CONFIG_CMD="./configure ${CONFIGUREOPTS} ${EXTRA_OECONF} --cross-compile"
if [ "${CROSS_METHOD}" = "answer" ]; then
--
2.38.1


Re: [meta-python][PATCH 2/2] python3-uefi-firmware: add recipe for version 1.9

Khem Raj
 

On 11/29/22 11:29 PM, tomzy wrote:
On Fri, Nov 25, 2022 at 3:44 AM tomzy <tomasz.zyjewski@...
<mailto:tomasz.zyjewski@...>> wrote:
Install uefi-firmware-parser tool
Signed-off-by: Tomasz Żyjewski <tomasz.zyjewski@...
<mailto:tomasz.zyjewski@...>>
---
 .../python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>         | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644
meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>
diff --git
a/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>
b/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>
new file mode 100644
index 000000000000..ba3124b36e60
--- /dev/null
+++
b/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
<http://python3-uefi-firmware_1.9.bb>
@@ -0,0 +1,17 @@
+SUMMARY = "Various data structures and parsing tools for UEFI
firmware."
+DESCRIPTION = "This package contains Python UEFI firmware parser
tool. The \
+UEFI firmware parser is a simple module and set of scripts for
parsing, \
+extracting, and recreating UEFI firmware volumes. This includes
parsing \
+modules for BIOS, OptionROM, Intel ME and other formats too."
+HOMEPAGE = "https://github.com/theopolis/uefi-firmware-parser
<https://github.com/theopolis/uefi-firmware-parser>"
+AUTHOR = "Teddy Reed <teddy@... <mailto:teddy@...>>"
+LICENSE = "BSD-2-Clause & BSD-3-Clause"
+LIC_FILES_CHKSUM =
"file://setup.py;md5=90fa5bae1547550f1c1993f651eda955"
+
+SRC_URI =
"https://files.pythonhosted.org/packages/7e/b4/a4ec646d24a1aad709fdb83de6e5eddd6cb24faec02f3a94a3af3b0aba28/uefi_firmware-${PV}.tar.gz <https://files.pythonhosted.org/packages/7e/b4/a4ec646d24a1aad709fdb83de6e5eddd6cb24faec02f3a94a3af3b0aba28/uefi_firmware-$%7BPV%7D.tar.gz>"
If you’re fetching from  pythonhosted, you could very likely
simplify the recipe by inheriting pypi bbclass
+SRC_URI[md5sum] = "ee5011b4d0bcb0eb7c06295e0107894f"
These days, we only really use the sha256sum
+SRC_URI[sha256sum] =
"234119dd92780c67cce3b664e86119c41d0b2af188d7f372b69789b32c5d5cd0" +
+S = "${WORKDIR}/uefi_firmware-${PV}" + +inherit setuptools3 -- 2.25.1
Used git fetcher here, I just send PATCH V2, not sure if it visible on mailing list.
Its not. Where did you send it ?