From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/15] package/pkg-cmake.mk: globally disable doc, examples and tests
Date: Sun, 19 Oct 2014 22:56:49 +0200 [thread overview]
Message-ID: <20141019225649.2f16bd37@free-electrons.com> (raw)
In-Reply-To: <CAHXCMMKCj2PoOrL0xGPRfp=FOhZm4=tN2RdPJR9J-J=_3ro_3w@mail.gmail.com>
Dear Samuel Martin,
On Sun, 19 Oct 2014 22:28:18 +0200, Samuel Martin wrote:
> > Are these options standardized by CMake, or are they just "generally"
> > used by a number of packages?
>
> Not standardized by CMake, just used by a number of packages.
>
> >
> > If not, I don't see why they should be passed by the
> > CMake infrastructure.
>
> Since we don't really care about these things, and don't want to be
> bothered by failure because of these features, I think it's a way to
> enforce disabling them.
And so, we will keep adding more and more options that are not CMake
standard options to the core CMake infrastructure?
I know we've done that for pkg-autotools, but I'm not sure it was such
a great idea. Especially, I'd like to understand where we will stop:
will we, when two packages have common options, move them to the common
infrastructure, even if those options are not CMake standard at all?
At least, I'd like to see what is our "policy" about this, and get some
feedback from other Buildroot developers on this.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-19 20:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 18:04 [Buildroot] [PATCH 00/15] CMake janitor Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 01/15] package/pkg-cmake.mk: globally disable doc, examples and tests Samuel Martin
2014-10-19 20:10 ` Thomas Petazzoni
2014-10-19 20:28 ` Samuel Martin
2014-10-19 20:56 ` Thomas Petazzoni [this message]
2014-10-20 8:34 ` Samuel Martin
2014-10-20 19:57 ` Arnout Vandecappelle
2014-10-19 18:04 ` [Buildroot] [PATCH 02/15] package/pkg-cmake.mk: disable colouring the output Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 03/15] package/clapack: cleanup configure options Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 04/15] package/flann: " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 05/15] package/libsoxr: " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 06/15] " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 07/15] package/libubox: cleanup dependencies Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 08/15] package/libubox: cleanup configure options Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 09/15] " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 10/15] package/libuci: " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 11/15] " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 12/15] package/ne10: " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 13/15] package/opencv: " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 14/15] package/polarssl: " Samuel Martin
2014-10-19 18:04 ` [Buildroot] [PATCH 15/15] docs/manual: update cmake-package infrastructure section Samuel Martin
2014-10-26 16:08 ` [Buildroot] [PATCH 00/15] CMake janitor 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=20141019225649.2f16bd37@free-electrons.com \
--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