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 v3 0/2] Add initial support for meson
Date: Wed, 28 Dec 2022 09:29:41 +0100	[thread overview]
Message-ID: <20221228082943.3599-1-dwagner@suse.de> (raw)

I had to fallback to use a workaround to install the man pages to the
correct directory. Meson insistet to install them into subdirs and
failed to install them when I forced Meson not to do this. I am sure I
am doing something wrong but couldn't figure out what. I think
it's okay to use the workaround until we figured how to do this
'correct'.

Tested this by packaging it up for OpenSUSE and the it looks
reasonable:

https://build.opensuse.org/project/show/home:wagi:branches:devel:tools

Changes:
v3:
  - generate tc_version.h file
  - lib: cleaning up the standalone build vs trace-cmd build
  - s/conf10.set/conf.set10/
  - default build target is debug
  - do not install man pages into subdirs

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/install-man.sh.in |  15 ++
 Documentation/libtracecmd/meson.build       | 148 +++++++++++++++++
 Documentation/trace-cmd/install-man.sh.in   |  10 ++
 Documentation/trace-cmd/meson.build         | 167 ++++++++++++++++++++
 lib/Documentation                           |   1 +
 lib/meson.build                             | 112 +++++++++++++
 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                   |  83 ++++++++++
 meson-vcs-tag.sh                            |  17 ++
 meson.build                                 | 144 +++++++++++++++++
 meson_options.txt                           |  25 +++
 python/meson.build                          |  40 +++++
 tracecmd/meson.build                        |  57 +++++++
 utest/meson.build                           |  25 +++
 16 files changed, 884 insertions(+)
 create mode 100755 Documentation/libtracecmd/install-man.sh.in
 create mode 100644 Documentation/libtracecmd/meson.build
 create mode 100755 Documentation/trace-cmd/install-man.sh.in
 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 100755 meson-vcs-tag.sh
 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-28  8:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28  8:29 Daniel Wagner [this message]
2022-12-28  8:29 ` [PATCH v3 1/2] libtracecmd: Add initial support for meson Daniel Wagner
2022-12-28  8:29 ` [PATCH v3 2/2] trace-cmd: " 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=20221228082943.3599-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).