From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v5] libtracefs: Add initial support for meson
Date: Wed, 4 Jan 2023 11:09:16 -0500 [thread overview]
Message-ID: <20230104110916.4f652a96@gandalf.local.home> (raw)
In-Reply-To: <20221228082927.3499-1-dwagner@suse.de>
On Wed, 28 Dec 2022 09:29:27 +0100
Daniel Wagner <dwagner@suse.de> wrote:
> Introduce Meson as build framework for building libtracefs. This
> lives besides the Makefiles until all the expected initial fallouts
> have been dealed with.
>
> The build steps are:
>
> # configure using .build as build directory and install destination
> # /tmp/test
> meson --prefix=/tmp/libtracefs .build
>
> # trigger the build
> ninja -C .build
>
> # install the library
> ninja -C .build install
>
> In case you want to build/install the documentation the setup is
>
> meson -Ddocs-build=true .build
>
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
This also doesn't build the static library libtracefs.a.
We have environments that we need to build trace-cmd statically. As
trace-cmd depends on libtraceevent and libtracefs, that means both need a
static library as well.
-- Steve
next prev parent reply other threads:[~2023-01-04 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 8:29 [PATCH v5] libtracefs: Add initial support for meson Daniel Wagner
2023-01-04 16:09 ` Steven Rostedt [this message]
2023-01-04 17:19 ` Daniel Wagner
2023-01-04 17:44 ` Steven Rostedt
2023-01-05 7:18 ` Daniel Wagner
2023-01-05 13:51 ` Steven Rostedt
2023-01-05 14:41 ` Daniel Wagner
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=20230104110916.4f652a96@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dwagner@suse.de \
--cc=linux-trace-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).