Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] linux/perf: build the host perf tool
Date: Sat, 19 Mar 2016 17:03:40 +0100	[thread overview]
Message-ID: <56ED785C.4050005@mind.be> (raw)
In-Reply-To: <20160319145515.32875737@free-electrons.com>

On 03/19/16 14:55, Thomas Petazzoni wrote:
> On Fri, 11 Mar 2016 19:19:59 +0100, Yann E. MORIN wrote:
>> >Currently, we only build the target variant of the perf tool. However,
>> >perf on the target may generate a bunch of data files that may have to
>> >be analysed on the host.
>> >
>> >There is no host-variant of the linux-tools infrastructure, so we just
>> >build the host perf at the same time we build the target one.
>> >
>> >Signed-off-by: "Yann E. MORIN"<yann.morin.1998@free.fr>
>> >Cc: Thomas De Schampheleire<patrickdepinguin@gmail.com>
> First of all, I have to say I hate this target package that builds and
> installs host stuff. But, since I don't have a better solution to
> offer, and it's anyway not the only package in this case (qt/qt5 are
> also target packages, and they install stuff in host), I'm fine with
> the general approach.

  I think it's OK to build and install host tools that are bound tightly with 
the target package. E.g. qmake only makes sense when you have qt for the target. 
perf is in the same boat.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  parent reply	other threads:[~2016-03-19 16:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 18:19 [Buildroot] [PATCH 0/6] linux: build host perf (branch yem/linux-host-perf) Yann E. MORIN
2016-03-11 18:19 ` [Buildroot] [PATCH 1/6] linux/perf: really do not build the documentation Yann E. MORIN
2016-03-11 18:19 ` [Buildroot] [PATCH 2/6] linux/perf: honour the number of parallel jobs Yann E. MORIN
2016-03-11 18:19 ` [Buildroot] [PATCH 3/6] linux/perf: forcefully disable the features with missing dependencies Yann E. MORIN
2016-03-11 18:19 ` [Buildroot] [PATCH 4/6] linux/perf: conditionally enable support for gz/xz compression Yann E. MORIN
2016-03-11 18:19 ` [Buildroot] [PATCH 5/6] linux/perf: build in a sub-directory Yann E. MORIN
2016-03-11 18:19 ` [Buildroot] [PATCH 6/6] linux/perf: build the host perf tool Yann E. MORIN
2016-03-19 13:55   ` Thomas Petazzoni
2016-03-19 14:23     ` Yann E. MORIN
2016-03-19 16:03     ` Arnout Vandecappelle [this message]
2016-03-19 13:48 ` [Buildroot] [PATCH 0/6] linux: build host perf (branch yem/linux-host-perf) 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=56ED785C.4050005@mind.be \
    --to=arnout@mind.be \
    --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