mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] nanopb: version bump 0.4.8 -> 0.4.9.1
Date: Fri,  7 Nov 2025 09:53:26 +0100	[thread overview]
Message-ID: <20251107085326.2208895-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251028143921.512916-4-s.pueschel@pengutronix.de>

Thanks, applied as 4a1a4c70b416ccf05df903d4abc07a1daafb0a6e.

Michael

[sent from post-receive hook]

On Fri, 07 Nov 2025 09:53:26 +0100, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> Set the CMake configure arguments based on the comment in the rule file
> that only headers, generators and static libraries are installed.
> Therefore disabled building a shared library. Also the static library
> depends on the BUILD_RUNTIME setting, which is therefore enabled.
> 
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20251028143921.512916-4-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/nanopb.make b/rules/nanopb.make
> index 4b592768830d..8df47f52d7c7 100644
> --- a/rules/nanopb.make
> +++ b/rules/nanopb.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_NANOPB) += nanopb
>  #
>  # Paths and names
>  #
> -NANOPB_VERSION		:= 0.4.8
> -NANOPB_MD5		:= 7c5305add7bf70b915c6eb1dc50cc20f
> +NANOPB_VERSION		:= 0.4.9.1
> +NANOPB_MD5		:= 97b043a99b26eb1722460ee4c826ddba
>  NANOPB			:= nanopb-$(NANOPB_VERSION)
>  NANOPB_SUFFIX		:= tar.gz
>  NANOPB_URL		:= https://jpa.kapsi.fi/nanopb/download/$(NANOPB).$(NANOPB_SUFFIX)
> @@ -33,7 +33,11 @@ NANOPB_LICENSE_FILES	:= file://LICENSE.txt;md5=9db4b73a55a3994384112efcdb37c01f
>  #
>  NANOPB_CONF_TOOL	:= cmake
>  NANOPB_CONF_OPT		:= \
> -	$(CROSS_CMAKE_USR)
> +	$(CROSS_CMAKE_USR) \
> +	-DBUILD_SHARED_LIBS=OFF \
> +	-DBUILD_STATIC_LIBS=ON \
> +	-Dnanopb_BUILD_GENERATOR=ON \
> +	-Dnanopb_BUILD_RUNTIME=ON
>  
>  # Note: the package installs only headers, generators, and static libraries, so
>  # no targetinstall stage is needed.



  reply	other threads:[~2025-11-07  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 14:38 [ptxdist] [PATCH 1/4] host-abseil-cpp: new package Sven Püschel
2025-10-28 14:38 ` [ptxdist] [PATCH 2/4] protobuf: version bump 3.7.1 -> 33.0 Sven Püschel
2025-11-07  8:53   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-10-28 14:38 ` [ptxdist] [PATCH 3/4] protobuf-c: version bump 1.4.1 -> 1.5.2 Sven Püschel
2025-11-07  8:53   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-10-28 14:38 ` [ptxdist] [PATCH 4/4] nanopb: version bump 0.4.8 -> 0.4.9.1 Sven Püschel
2025-11-07  8:53   ` Michael Olbrich [this message]
2025-11-07  8:53 ` [ptxdist] [APPLIED] host-abseil-cpp: new package Michael Olbrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251107085326.2208895-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=s.pueschel@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox