From: Jan Heylen <heyleke@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 0/3] Opentracing-cpp: new package
Date: Wed, 3 Jan 2018 22:20:08 +0100 [thread overview]
Message-ID: <1515014411-3504-1-git-send-email-heyleke@gmail.com> (raw)
From: Jan Heylen <jan.heylen@nokia.com>
Hi,
V5 of "this adds opentracing-cpp package as a logging library package."
Removed generalisation of pkg-cmake stuff related to shared/static stuff again and added note in pkg-cmake.mk why.
br,
Jan
Jan Heylen (3):
rabbitmq-c: BUILD_SHARED_LIBS is handled in pkg-cmake.mk
pkg-cmake: add note on BUILD_STATIC_LIBS
opentracing-cpp: new package
DEVELOPERS | 3 +
package/Config.in | 1 +
...shared-static-target-a-configurable-optio.patch | 74 ++++++++++++++++++++++
package/opentracing-cpp/Config.in | 16 +++++
package/opentracing-cpp/opentracing-cpp.hash | 3 +
package/opentracing-cpp/opentracing-cpp.mk | 25 ++++++++
package/pkg-cmake.mk | 9 +++
package/rabbitmq-c/rabbitmq-c.mk | 7 +-
8 files changed, 135 insertions(+), 3 deletions(-)
create mode 100644 package/opentracing-cpp/0001-CMake-make-shared-static-target-a-configurable-optio.patch
create mode 100644 package/opentracing-cpp/Config.in
create mode 100644 package/opentracing-cpp/opentracing-cpp.hash
create mode 100644 package/opentracing-cpp/opentracing-cpp.mk
--
2.7.4
next reply other threads:[~2018-01-03 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 21:20 Jan Heylen [this message]
2018-01-03 21:20 ` [Buildroot] [PATCH v5 1/3] rabbitmq-c: BUILD_SHARED_LIBS is handled in pkg-cmake.mk Jan Heylen
2018-01-03 21:20 ` [Buildroot] [PATCH v5 2/3] pkg-cmake: add note on BUILD_STATIC_LIBS Jan Heylen
2018-01-03 21:20 ` [Buildroot] [PATCH v5 3/3] opentracing-cpp: new package Jan Heylen
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=1515014411-3504-1-git-send-email-heyleke@gmail.com \
--to=heyleke@gmail.com \
--cc=buildroot@busybox.net \
/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