From: Ingo Molnar <mingo@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, acme@infradead.org,
Andi Kleen <ak@linux.intel.com>,
Namhyung Kim <namhyung.kim@lge.com>,
peterz@infradead.org
Subject: Re: [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable
Date: Mon, 5 Aug 2013 11:12:21 +0200 [thread overview]
Message-ID: <20130805091221.GB26940@gmail.com> (raw)
In-Reply-To: <87fvuozerv.fsf@sejong.aot.lge.com>
* Namhyung Kim <namhyung@kernel.org> wrote:
> Hi,
>
> On Mon, 5 Aug 2013 01:23:20 -0700, Christoph Hellwig wrote:
> > On Mon, Aug 05, 2013 at 10:16:41AM +0200, Ingo Molnar wrote:
> >> If you want fewer dependencies then build with 'make NO_GTK=1'.
> >
> > Doesn't help the distros. Installing perf and pulling all the
> > graphics libraries in is highly annoying, especially in size
> > constrained VM or Cloud images. Having a separate binary or at least
> > an ldopen()able plugin that can go into a separate package is highly
> > desirable.
>
> I wrote a patch series [1] separating gtk code to a dso and use it with
> libdl last year. But I didn't get much feedback probably due to the
> mistake of not installing the dso to a proper place. It'd be great if
> you guys take a look at it and give some comments.
>
> Thanks,
> Namhyung
>
>
> [1] https://lkml.org/lkml/2012/11/14/510
Assuming that in the normal case it can be made to work like a full build
of perf today (i.e. without forcing LD_PRELOAD) then splitting the
libraries away looks like a much better solution than splitting the
binary.
Thanks,
Ingo
next prev parent reply other threads:[~2013-08-05 9:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 2:22 [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable Andi Kleen
2013-08-05 8:16 ` Ingo Molnar
2013-08-05 8:23 ` Christoph Hellwig
2013-08-05 8:31 ` Ingo Molnar
2013-08-05 8:34 ` Christoph Hellwig
2013-08-05 9:08 ` Ingo Molnar
2013-08-06 6:19 ` Christoph Hellwig
2013-08-12 18:19 ` Ingo Molnar
2013-08-12 19:25 ` Vince Weaver
2013-08-13 10:48 ` Ingo Molnar
2013-08-13 12:11 ` Arnaldo Carvalho de Melo
2013-08-13 16:00 ` Ingo Molnar
2013-08-13 21:57 ` Vince Weaver
2013-08-13 22:17 ` Andi Kleen
2013-08-14 14:13 ` Arnaldo Carvalho de Melo
2013-08-14 14:20 ` Ingo Molnar
2013-08-13 14:03 ` Vince Weaver
2013-08-13 16:04 ` Ingo Molnar
2013-08-05 9:08 ` Namhyung Kim
2013-08-05 9:12 ` Ingo Molnar [this message]
2013-08-05 9:18 ` Pekka Enberg
2013-08-05 19:10 ` Andi Kleen
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=20130805091221.GB26940@gmail.com \
--to=mingo@kernel.org \
--cc=acme@infradead.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.