From: Roland Hieber <rhi@pengutronix.de>
To: Denis OSTERLAND-HEIM <denis.osterland@diehl.com>
Cc: Ian Abbott <abbotti@mev.co.uk>,
"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [EXT] [PATCH] protobuf-c: new package
Date: Thu, 9 Mar 2023 14:24:50 +0100 [thread overview]
Message-ID: <20230309132450.5vnerymz2zdlyb4y@pengutronix.de> (raw)
In-Reply-To: <267946fb4b1f418eaeca561e00299b89@diehl.com>
On Fri, Jan 27, 2023 at 09:57:28AM +0100, Denis OSTERLAND-HEIM wrote:
> Hi,
>
> -----Original Message-----
> From: ptxdist <ptxdist-bounces@pengutronix.de> On Behalf Of Ian Abbott
> Sent: Wednesday, January 25, 2023 2:38 PM
> To: ptxdist@pengutronix.de
> Cc: Ian Abbott <abbotti@mev.co.uk>
> Subject: [EXT] [ptxdist] [PATCH] protobuf-c: new package
>
> [EXTERNAL EMAIL]
>
>
> Also host-protobuf-c. The C code generator plug-in for protoc is only built
> for the host package.
>
> Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
> ---
> rules/host-protobuf-c.in | 6 ++++
> rules/host-protobuf-c.make | 22 ++++++++++++++
> rules/protobuf-c.in | 13 +++++++++
> rules/protobuf-c.make | 59 ++++++++++++++++++++++++++++++++++++++
> 4 files changed, 100 insertions(+)
> create mode 100644 rules/host-protobuf-c.in create mode 100644
> rules/host-protobuf-c.make create mode 100644 rules/protobuf-c.in create
> mode 100644 rules/protobuf-c.make
>
[...]
> diff --git a/rules/protobuf-c.make b/rules/protobuf-c.make new file mode
> 100644 index 000000000..60f7f6494
> --- /dev/null
> +++ b/rules/protobuf-c.make
> @@ -0,0 +1,59 @@
> +# -*-makefile-*-
> +#
> +# Copyright (C) 2023 by Ian Abbott <abbotti@mev.co.uk> # # For further
> +information about the PTXdist project and license conditions # see the
> +README file.
> +#
> +
> +#
> +# We provide this package
> +#
> +PACKAGES-$(PTXCONF_PROTOBUF_C) += protobuf-c
> +
> +#
> +# Paths and names
> +#
> +PROTOBUF_C_VERSION := 1.4.1
> +PROTOBUF_C_MD5 := 4c17d70317ce9fc4cca9690377284659
> +PROTOBUF_C := protobuf-c-$(PROTOBUF_C_VERSION)
> +PROTOBUF_C_SUFFIX := tar.gz
> +PROTOBUF_C_URL :=
> https://github.com/protobuf-c/protobuf-c/releases/download/v$(PROTOBUF_C_VER
> SION)/protobuf-c-$(PROTOBUF_C_VERSION).$(PROTOBUF_C_SUFFIX)
> +PROTOBUF_C_SOURCE := $(SRCDIR)/$(PROTOBUF_C).$(PROTOBUF_C_SUFFIX)
> +PROTOBUF_C_DIR := $(BUILDDIR)/$(PROTOBUF_C)
> +PROTOBUF_C_LICENSE := BSD-2-Clause
> +PROTOBUF_C_LICENSE_FILES :=
> +file://LICENSE;md5=9f725889e0d77383e26cb42b0b62cea2
> +
> +#
> +-----------------------------------------------------------------------
> +-----
> +# Prepare
> +#
> +-----------------------------------------------------------------------
> +-----
> +
> +#
> +# autoconf
> +#
> +PROTOBUF_C_CONF_TOOL := autoconf
> +PROTOBUF_C_CONF_OPT := \
> + $(CROSS_AUTOCONF_USR) \
> + --disable-protoc \
> + --disable-static
> Is there a reason why static is disabled fort he target?
All packages in PTXdist do this. There is no need to use static
libraries on a system that supports dynamic libraries.
- Roland
> Regards, Denis
> +
> +#
> +-----------------------------------------------------------------------
> +-----
> +# Target-Install
> +#
> +-----------------------------------------------------------------------
> +-----
> +
> +$(STATEDIR)/protobuf-c.targetinstall:
> + @$(call targetinfo)
> +
> + @$(call install_init, protobuf-c)
> + @$(call install_fixup, protobuf-c,PRIORITY,optional)
> + @$(call install_fixup, protobuf-c,SECTION,base)
> + @$(call install_fixup, protobuf-c,AUTHOR,"Ian Abbott
> <abbotti@mev.co.uk>")
> + @$(call install_fixup, protobuf-c,DESCRIPTION,missing)
> +
> + @$(call install_lib, protobuf-c, 0, 0, 0644, libprotobuf-c)
> +
> + @$(call install_finish, protobuf-c)
> +
> + @$(call touch)
> +
> +# vim: syntax=make
> --
> 2.39.0
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-03-09 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 8:57 Denis OSTERLAND-HEIM
2023-03-09 13:24 ` Roland Hieber [this message]
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=20230309132450.5vnerymz2zdlyb4y@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=abbotti@mev.co.uk \
--cc=denis.osterland@diehl.com \
--cc=ptxdist@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