From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] opentracing-cpp: new package
Date: Wed, 3 Jan 2018 21:44:03 +0100 [thread overview]
Message-ID: <20180103214403.04e54ec6@windsurf.lan> (raw)
In-Reply-To: <CAHXCMMJo24SinfZnTfbee5X3MjfF31cYHEJkH9=dJ=TmZpDDZg@mail.gmail.com>
Hello,
On Wed, 3 Jan 2018 21:37:03 +0100, Samuel Martin wrote:
> > On the other hand, there doesn't seem to be a real standardization of
> > such options in the CMake world. I.e it's really up to each individual
> > package to obey to BUILD_SHARED_LIBS/BUILD_STATIC_LIBS, and many CMake
> > packages have their own custom options to enable/disable shared/static
> > library build.
> >
> > But I guess for the sake of consistency pkg-cmake.mk should also pass
> > BUILD_STATIC_LIBS, and we should accordingly cleanup the CMake packages
> > that rely on BUILD_SHARED_LIBS/BUILD_STATIC_LIBS to not pass them
> > explicitly, and rely on what the pkg-cmake infra is doing.
>
> Adding BUILD_STATIC_LIBS will make thing a bit nicer (at least
> symetric), though it is not standard in any way, which means some
> projects may choose another name for a similar option and there is not
> much we can do about this.
>
> BTW, some projects still seems ignoring the existence of the
> BUILD_SHARED_LIBS variable since they add a similar option with a
> different name.
>
>
> [1] https://cmake.org/cmake/help/v3.8/manual/cmake-variables.7.html#variables-that-change-behavior
So BUILD_SHARED_LIBS is somewhat standardized by CMake, but not
BUILD_STATIC_LIBS.
If that's the case, then we should not handle BUILD_STATIC_LIBS in
pkg-cmake.mk, contrary to what I said previously. And we should add a
comment explaining this in pkg-cmake.mk.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-03 20:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 9:41 [Buildroot] Opentracing-cpp package heyleke at gmail.com
2017-12-21 9:41 ` [Buildroot] [PATCH] Opentracing: add opentracing-cpp v1.2.0 package heyleke at gmail.com
2017-12-22 15:00 ` Samuel Martin
2017-12-22 15:20 ` Jan Heylen
2017-12-23 7:40 ` [Buildroot] [PATCH v2 0/2] Opentracing-cpp: new package Jan Heylen
2017-12-23 7:40 ` [Buildroot] [PATCH v2 1/2] Opentracing: add opentracing-cpp v1.2.0 package Jan Heylen
2017-12-30 21:46 ` Thomas Petazzoni
2017-12-30 21:49 ` Jan Heylen
2017-12-31 9:23 ` Jan Heylen
2017-12-31 10:46 ` Jan Heylen
2017-12-31 13:23 ` Jan Heylen
2017-12-31 16:10 ` Thomas Petazzoni
2017-12-31 17:57 ` Jan Heylen
2018-01-03 8:52 ` [Buildroot] [PATCH v3 0/1] Opentracing-cpp: new package Jan Heylen
2018-01-03 8:52 ` [Buildroot] [PATCH v3 1/1] opentracing-cpp: " Jan Heylen
2018-01-03 9:03 ` Baruch Siach
2018-01-03 9:07 ` Jan Heylen
2018-01-03 9:50 ` Baruch Siach
2018-01-03 10:10 ` Thomas Petazzoni
2018-01-03 20:37 ` Samuel Martin
2018-01-03 20:44 ` Thomas Petazzoni [this message]
2017-12-23 7:40 ` [Buildroot] [PATCH v2 2/2] opentracing-cpp: make shared/static target a configurable option Jan Heylen
2017-12-29 17:23 ` Jan Heylen
2017-12-30 21:47 ` Thomas Petazzoni
2017-12-30 21:44 ` [Buildroot] [PATCH v2 0/2] Opentracing-cpp: new package Thomas Petazzoni
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=20180103214403.04e54ec6@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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