linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <dwagner@suse.de>
To: linux-trace-devel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>, Daniel Wagner <dwagner@suse.de>
Subject: [PATCH v2 0/2] Add initial support for meson
Date: Fri, 23 Dec 2022 11:15:00 +0100	[thread overview]
Message-ID: <20221223101502.12269-1-dwagner@suse.de> (raw)

This version is intergrating the libtracecmd static build directly
inside trace-cmd build. That means you don't need to build and install
libtracecmd first to be able to build trace-cmd. This should simplify
the development workflow.

The shared libtracecmd build is still possible and modelled as it's
own project (lib/meson.build).

With this, there is no need to change anything in the current project
layout or development work flow, which I assume is helping getting
meson added :)

Changes:
v2:
  - make audit dependency optional as default
  - integrate static libtracecmd build into trace-cmd directly
  - remove check-manpages target in trace-cmd

v1:
  - initial version

Daniel Wagner (2):
  libtracecmd: Add initial support for meson
  trace-cmd: Add initial support for meson

 Documentation/libtracecmd/meson.build     | 117 +++++++++++++++++++++
 Documentation/list-txt.sh                 |   5 +
 Documentation/trace-cmd/meson.build       | 117 +++++++++++++++++++++
 lib/Documentation                         |   1 +
 lib/meson.build                           | 109 ++++++++++++++++++++
 lib/meson_options.txt                     |  21 ++++
 lib/trace-cmd/include/meson.build         |   5 +
 lib/trace-cmd/include/private/meson.build |  14 +++
 lib/trace-cmd/meson.build                 |  81 +++++++++++++++
 meson.build                               | 119 ++++++++++++++++++++++
 meson_options.txt                         |  23 +++++
 python/meson.build                        |  40 ++++++++
 tracecmd/meson.build                      |  55 ++++++++++
 utest/meson.build                         |  25 +++++
 14 files changed, 732 insertions(+)
 create mode 100644 Documentation/libtracecmd/meson.build
 create mode 100644 Documentation/list-txt.sh
 create mode 100644 Documentation/trace-cmd/meson.build
 create mode 120000 lib/Documentation
 create mode 100644 lib/meson.build
 create mode 100644 lib/meson_options.txt
 create mode 100644 lib/trace-cmd/include/meson.build
 create mode 100644 lib/trace-cmd/include/private/meson.build
 create mode 100644 lib/trace-cmd/meson.build
 create mode 100644 meson.build
 create mode 100644 meson_options.txt
 create mode 100644 python/meson.build
 create mode 100644 tracecmd/meson.build
 create mode 100644 utest/meson.build

-- 
2.39.0


             reply	other threads:[~2022-12-23 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23 10:15 Daniel Wagner [this message]
2022-12-23 10:15 ` [PATCH v2 1/2] libtracecmd: Add initial support for meson Daniel Wagner
2022-12-23 19:25   ` Steven Rostedt
2022-12-24 10:32     ` Daniel Wagner
2022-12-23 10:15 ` [PATCH v2 2/2] trace-cmd: " Daniel Wagner
2022-12-23 16:18   ` Steven Rostedt
2022-12-23 16:24     ` Steven Rostedt
2022-12-24 10:34       ` 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=20221223101502.12269-1-dwagner@suse.de \
    --to=dwagner@suse.de \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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).