All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ziegler <br015@umbiko.net>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Pierre Floury <pierre.floury@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/4] package/libtraceevent: new package
Date: Sun, 05 Feb 2023 09:20:15 +0100	[thread overview]
Message-ID: <bd47b6d90e460842dbe8252016f2b077@umbiko.net> (raw)
In-Reply-To: <mailman.18015.1675100677.179342.buildroot@buildroot.org>

Hi Maxime,

libtraceevent and libtracefs are libraries, thus should be positioned 
under "Target packages" -> "Libraries".

Introducing a "Debugging, profiling and benchmark" category here would 
probably be appropriate.

Tested successfully on x86_64 hardware.

Kind regards,
Andreas

On 2023-01-30 18:44, Maxime Chevallier wrote:
> 
> Introduce the libtraceevent library, that used to be bundled with the
> trace-cmd tool. This library is now used by several tools and libraries
> such as trace-cmd, libtracefs and rtla.
> 
> This package tries to install libraries in /usr/local/lib by default,
> hence the redefinition of the "prefix" variable, so that the library
> gets installed in "/usr/lib" instead.
> 
> The same applies to the pkgconfig handling of the proved Makefile, 
> which
> installs the .pc files in the /usr/local area by default, hence the
> redefinition of the pkgconfig_dir to either the correct directory 
> within the
> staging area, or to empty value for the target to avoid installing the 
> .pc
> in that case.
> 
> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> ---
>  DEVELOPERS                             |  3 +++
>  package/Config.in                      |  1 +
>  package/libtraceevent/Config.in        |  9 +++++++
>  package/libtraceevent/libtraceevent.mk | 33 ++++++++++++++++++++++++++
>  4 files changed, 46 insertions(+)
>  create mode 100644 package/libtraceevent/Config.in
>  create mode 100644 package/libtraceevent/libtraceevent.mk
> 
> diff --git a/DEVELOPERS b/DEVELOPERS
> index 706ee80ece..fcf05e0aa0 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -2106,6 +2106,9 @@ F:	package/postgresql/
>  F:	package/protozero/
>  F:	package/timescaledb/
> 
> +N:	Maxime Chevallier <maxime.chevallier@bootlin.com>
> +F:	package/libtraceevent/
> +
>  N:	Michael Durrant <mdurrant@arcturusnetworks.com>
>  F:	board/arcturus/
>  F:	configs/arcturus_ucp1020_defconfig
> diff --git a/package/Config.in b/package/Config.in
> index 83fddf316f..2f0e6dcb18 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -117,6 +117,7 @@ menu "Debugging, profiling and benchmark"
>  	source "package/kyua/Config.in"
>  	source "package/latencytop/Config.in"
>  	source "package/libbpf/Config.in"
> +	source "package/libtraceevent/Config.in"
>  	source "package/lmbench/Config.in"
>  	source "package/lsof/Config.in"
>  	source "package/ltp-testsuite/Config.in"
> diff --git a/package/libtraceevent/Config.in 
> b/package/libtraceevent/Config.in
> new file mode 100644
> index 0000000000..d351e3b4de
> --- /dev/null
> +++ b/package/libtraceevent/Config.in
> @@ -0,0 +1,9 @@
> +config BR2_PACKAGE_LIBTRACEEVENT
> +	bool "libtraceevent"
> +	help
> +	  libtraceevent is a library that interfaces with the ftrace
> +	  subsystem in the linux kernel.
> +	  It used to be bundled directly in the trace-cmd
> +	  tool, but it was eventually extracted so that it can be used
> +	  by multiple other tools and libraries, such as libtracefs and
> +	  rtla.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

       reply	other threads:[~2023-02-05  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.18015.1675100677.179342.buildroot@buildroot.org>
2023-02-05  8:20 ` Andreas Ziegler [this message]
2023-02-06  7:34   ` [Buildroot] [PATCH 1/4] package/libtraceevent: new package Maxime Chevallier via buildroot
2023-02-05  8:22 ` [Buildroot] [PATCH 3/4] package/linux-tools: add rtla Andreas Ziegler
2023-02-06  7:39   ` Maxime Chevallier via buildroot
2023-02-20 10:11     ` Andreas Ziegler
2023-01-30 14:46 [Buildroot] [PATCH 0/4] introduce the rtla package and its dependencies Maxime Chevallier via buildroot
2023-01-30 14:46 ` [Buildroot] [PATCH 1/4] package/libtraceevent: new package Maxime Chevallier via buildroot
2023-05-14 14:01   ` Yann E. MORIN

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=bd47b6d90e460842dbe8252016f2b077@umbiko.net \
    --to=br015@umbiko.net \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=pierre.floury@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.