Re: [ptxdist] [PATCH] host-qrencode: New package
Please do not apply. Will send a v2. On Thu, Mar 09, 2023 at 07:47:34AM +0100, Thorsten Scherer wrote: > Signed-off-by: Thorsten Scherer > --- > host-qrencode.in | 22 ++ > host-qrencode.make | 29 + > 2 files changed, 51 insertions(+) > create mode 100644 host-qrencode.in > create mode 100644 host-qrencode.make > > diff --git a/host-qrencode.in b/host-qrencode.in > new file mode 100644 > index 0..3ac6e7674 > --- /dev/null > +++ b/host-qrencode.in > @@ -0,0 +1,22 @@ > +## SECTION=hosttools_noprompt > +## SECTION=hosttools_platform > + > +config HOST_QRENCODE > + tristate > + select HOST_LIBPNG if HOST_QRENCODE_TOOLS > + help > + Libqrencode is a C library for encoding data in a QR Code symbol, a > + kind of 2D symbology that can be scanned by handy terminals such as a > + mobile phone with CCD. > + > +if HOST_QRENCODE > + > +config HOST_QRENCODE_TOOLS > + bool > + help > + Enable this option to build the qrencode tool to build QR codes from > + the command line. > + > +endif > + > +# vim: ft=kconfig ts=8 noet tw=80 > diff --git a/host-qrencode.make b/host-qrencode.make > new file mode 100644 > index 0..5fce96e00 > --- /dev/null > +++ b/host-qrencode.make > @@ -0,0 +1,29 @@ > +# -*-makefile-*- > +# > +# Copyright (C) 2023 by Thorsten Scherer > +# > +# For further information about the PTXdist project and license conditions > +# see the README file. > +# > + > +# > +# We provide this package > +# > +HOST_PACKAGES-$(PTXCONF_HOST_QRENCODE) += host-qrencode > + > +# > > +# Prepare > +# > > + > +HOST_QRENCODE_CONF_TOOL := autoconf > + > +# > > +# Install > +# > > + > +# Use = instead of := because host-qrencode.make being included before > qrencode.make > +HOST_QRENCODE_INSTALL_OPT= \ > + $(HOST_ENV) \ > + prefix=$(HOST_QRENCODE_PKGDIR)/usr \ > + > +# vim: syntax=make > -- > 2.38.0 >
[ptxdist] [PATCH] host-qrencode: New package
Signed-off-by: Thorsten Scherer --- host-qrencode.in | 22 ++ host-qrencode.make | 29 + 2 files changed, 51 insertions(+) create mode 100644 host-qrencode.in create mode 100644 host-qrencode.make diff --git a/host-qrencode.in b/host-qrencode.in new file mode 100644 index 0..3ac6e7674 --- /dev/null +++ b/host-qrencode.in @@ -0,0 +1,22 @@ +## SECTION=hosttools_noprompt +## SECTION=hosttools_platform + +config HOST_QRENCODE + tristate + select HOST_LIBPNG if HOST_QRENCODE_TOOLS + help + Libqrencode is a C library for encoding data in a QR Code symbol, a + kind of 2D symbology that can be scanned by handy terminals such as a + mobile phone with CCD. + +if HOST_QRENCODE + +config HOST_QRENCODE_TOOLS + bool + help + Enable this option to build the qrencode tool to build QR codes from + the command line. + +endif + +# vim: ft=kconfig ts=8 noet tw=80 diff --git a/host-qrencode.make b/host-qrencode.make new file mode 100644 index 0..5fce96e00 --- /dev/null +++ b/host-qrencode.make @@ -0,0 +1,29 @@ +# -*-makefile-*- +# +# Copyright (C) 2023 by Thorsten Scherer +# +# For further information about the PTXdist project and license conditions +# see the README file. +# + +# +# We provide this package +# +HOST_PACKAGES-$(PTXCONF_HOST_QRENCODE) += host-qrencode + +# +# Prepare +# + +HOST_QRENCODE_CONF_TOOL:= autoconf + +# +# Install +# + +# Use = instead of := because host-qrencode.make being included before qrencode.make +HOST_QRENCODE_INSTALL_OPT = \ + $(HOST_ENV) \ + prefix=$(HOST_QRENCODE_PKGDIR)/usr \ + +# vim: syntax=make -- 2.38.0
Re: [ptxdist] Image package creating several files
Hi Christian, El mié, 8 mar 2023 a las 18:49, Christian Melki () escribió: > > Hi. > > On 3/8/23 16:56, Guillermo Rodriguez Garcia wrote: > > Hello all, > > > > I have created an image package that signs some files. > > This package creates two separate files. > > > > What is the recommended way to handle this? From the documentation > > (https://www.ptxdist.org/doc/ref_make_variables.html#image-packages), > > I believe that _IMAGE is expected to contain the filename of one > > single file. For example the "clean" target uses this to know which > > file to delete. > > > > How can this be adapted for cases where more than one file is generated? > > > > Not sure what you mean by _IMAGE. But iirc, > barebox (etc) image installing packages handle this. > The rules can install multiple files into image directories and are > capable of cleaning up after themselves. Yes but that is a "regular" package. I am referring to "image packages", which are a bit different; see the documentation here: https://www.ptxdist.org/doc/ref_make_variables.html#image-packages In these packages, the _IMAGE variable points to a file (the image that is created by the rule). The clean target is automatically generated based on this variable. My question is how to do this if the package generates more than one image. BR, Guillermo Rodriguez Garcia guille.rodrig...@gmail.com
Re: [ptxdist] Image package creating several files
Hi. On 3/8/23 16:56, Guillermo Rodriguez Garcia wrote: > Hello all, > > I have created an image package that signs some files. > This package creates two separate files. > > What is the recommended way to handle this? From the documentation > (https://www.ptxdist.org/doc/ref_make_variables.html#image-packages), > I believe that _IMAGE is expected to contain the filename of one > single file. For example the "clean" target uses this to know which > file to delete. > > How can this be adapted for cases where more than one file is generated? > Not sure what you mean by _IMAGE. But iirc, barebox (etc) image installing packages handle this. The rules can install multiple files into image directories and are capable of cleaning up after themselves. > Thanks, > > Guillermo Rodriguez Garcia > guille.rodrig...@gmail.com >
[ptxdist] Image package creating several files
Hello all, I have created an image package that signs some files. This package creates two separate files. What is the recommended way to handle this? From the documentation (https://www.ptxdist.org/doc/ref_make_variables.html#image-packages), I believe that _IMAGE is expected to contain the filename of one single file. For example the "clean" target uses this to know which file to delete. How can this be adapted for cases where more than one file is generated? Thanks, Guillermo Rodriguez Garcia guille.rodrig...@gmail.com
[ptxdist] [PATCH] rauc: version bump 1.8 -> 1.9
RAUC switched to meson as the main build system but kept autotools for this release to ease migration. Since the meson-generated artifact does not have a 'configure' file, a separate autools release tarball was created that is used here. Signed-off-by: Enrico Jorns --- rules/rauc.make | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rules/rauc.make b/rules/rauc.make index cac186a64..0502fd370 100644 --- a/rules/rauc.make +++ b/rules/rauc.make @@ -14,11 +14,11 @@ PACKAGES-$(PTXCONF_RAUC) += rauc # # Paths and names # -RAUC_VERSION := 1.8 -RAUC_MD5 := acd0e788d804bda6645a2506c1068789 +RAUC_VERSION := 1.9 +RAUC_MD5 := 5b6ca0032185828f8f22d9a416319c3a RAUC := rauc-$(RAUC_VERSION) RAUC_SUFFIX:= tar.xz -RAUC_URL := https://github.com/rauc/rauc/releases/download/v$(RAUC_VERSION)/$(RAUC).$(RAUC_SUFFIX) +RAUC_URL := https://github.com/rauc/rauc/releases/download/v$(RAUC_VERSION)/$(RAUC)-autotools.$(RAUC_SUFFIX) RAUC_SOURCE:= $(SRCDIR)/$(RAUC).$(RAUC_SUFFIX) RAUC_DIR := $(BUILDDIR)/$(RAUC) RAUC_LICENSE := LGPL-2.1-only -- 2.30.2
