mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Cc: Clemens Gruber <clemens.gruber@pqgruber.com>
Subject: [ptxdist] [RFC 0/1] grpc
Date: Sun,  7 Oct 2018 17:54:57 +0200	[thread overview]
Message-ID: <20181007155458.23920-1-clemens.gruber@pqgruber.com> (raw)

Hi,

I am sending the current state of my grpc package for PTXdist.

gRPC is a RPC library, using HTTP/2 and protocol buffers. See grpc.io
for more information.

Because I am not entirely happy with it, I am flagging it as RFC.

Pain points:
- I had to patch the template-generated Makefile for cross-compiling
  (separate target and host packages), see patch 3
- I had to patch version numbers in said Makefile, see patch 4

I tested it successfully with an in-house C++ application which uses
gRPC and the meson build system. I could also send another patch, adding
support for the collectd grpc plugin, for PTXdist to have a testcase
within.

When building the host package, there are several warnings about the
missing c-ares, but it just falls back to using getaddrinfo and is not
important for the host tools/plugins, in my opinion. Also, host-openssl
and host-zlib is not necessary, so the warnings can be ignored.

Would be great if some of you could test it and maybe suggest
improvements.

Thanks,
Clemens

Clemens Gruber (1):
  grpc: new package

 ...rtability-test-for-c-and-make-it-pas.patch | 41 ++++++++++
 ...vent-shell-calls-longer-than-ARG_MAX.patch | 71 ++++++++++++++++
 ...d-proto-plugins-when-cross-compiling.patch | 25 ++++++
 ...0004-Fix-libgrpc-major-version-links.patch | 72 +++++++++++++++++
 patches/grpc-1.15.1/series                    |  7 ++
 rules/grpc.in                                 | 19 +++++
 rules/grpc.make                               | 80 +++++++++++++++++++
 rules/host-grpc.in                            |  6 ++
 rules/host-grpc.make                          | 30 +++++++
 9 files changed, 351 insertions(+)
 create mode 100644 patches/grpc-1.15.1/0001-Add-a-gcc-8.1-portability-test-for-c-and-make-it-pas.patch
 create mode 100644 patches/grpc-1.15.1/0002-Prevent-shell-calls-longer-than-ARG_MAX.patch
 create mode 100644 patches/grpc-1.15.1/0003-Do-not-build-proto-plugins-when-cross-compiling.patch
 create mode 100644 patches/grpc-1.15.1/0004-Fix-libgrpc-major-version-links.patch
 create mode 100644 patches/grpc-1.15.1/series
 create mode 100644 rules/grpc.in
 create mode 100644 rules/grpc.make
 create mode 100644 rules/host-grpc.in
 create mode 100644 rules/host-grpc.make

-- 
2.19.1


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2018-10-07 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-07 15:54 Clemens Gruber [this message]
2018-10-07 15:54 ` [ptxdist] [RFC 1/1] grpc: new package Clemens Gruber

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=20181007155458.23920-1-clemens.gruber@pqgruber.com \
    --to=clemens.gruber@pqgruber.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