From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v6] libtraceevent: Add initial support for meson
Date: Mon, 9 Jan 2023 10:56:16 -0500 [thread overview]
Message-ID: <20230109105616.168057c3@gandalf.local.home> (raw)
In-Reply-To: <20230105121144.11829-1-dwagner@suse.de>
On Thu, 5 Jan 2023 13:11:44 +0100
Daniel Wagner <dwagner@suse.de> wrote:
> Introduce Meson as build framework for building libtraceevent.
>
> The build steps are:
>
> # configure using .build as build directory and install destination
> # /tmp/test
> meson setup --prefix=/tmp/libtraceevent .build
>
> # trigger the build
> meson compile -C .build
>
> # In case you want to build the documentation, trigger the
> # build via the 'docs' target:
> meson compile -C build docs
>
> # install the library (and documentation)
> meson install -C .build
So I followed the above steps, and when I did:
$ ls -l /tmp/libtraceevent
total 1108
drwxr-xr-x 3 rostedt rostedt 60 Jan 9 10:49 lib
drwxr-xr-x 3 rostedt rostedt 60 Jan 9 10:49 include
drwxr-xr-x 3 rostedt rostedt 60 Jan 9 10:49 share
-rw-r--r-- 1 rostedt rostedt 23539 Jan 9 10:49 libtraceevent-set_flag.html
-rw-r--r-- 1 rostedt rostedt 31026 Jan 9 10:49 libtraceevent-parse-files.html
-rw-r--r-- 1 rostedt rostedt 36636 Jan 9 10:49 libtraceevent.html
-rw-r--r-- 1 rostedt rostedt 21390 Jan 9 10:49 libtraceevent-cpus.html
-rw-r--r-- 1 rostedt rostedt 23962 Jan 9 10:49 libtraceevent-header_page.html
-rw-r--r-- 1 rostedt rostedt 21790 Jan 9 10:49 libtraceevent-endian_read.html
-rw-r--r-- 1 rostedt rostedt 32679 Jan 9 10:49 libtraceevent-reg_event_handler.html
-rw-r--r-- 1 rostedt rostedt 24278 Jan 9 10:49 libtraceevent-event_find.html
-rw-r--r-- 1 rostedt rostedt 23586 Jan 9 10:49 libtraceevent-host_endian.html
-rw-r--r-- 1 rostedt rostedt 23775 Jan 9 10:49 libtraceevent-handle.html
-rw-r--r-- 1 rostedt rostedt 30738 Jan 9 10:49 libtraceevent-tseq.html
-rw-r--r-- 1 rostedt rostedt 35979 Jan 9 10:49 libtraceevent-filter.html
-rw-r--r-- 1 rostedt rostedt 48365 Jan 9 10:49 libtraceevent-kvm-plugin.html
-rw-r--r-- 1 rostedt rostedt 25273 Jan 9 10:49 libtraceevent-event_list.html
-rw-r--r-- 1 rostedt rostedt 22342 Jan 9 10:49 libtraceevent-page_size.html
-rw-r--r-- 1 rostedt rostedt 37832 Jan 9 10:49 libtraceevent-kbuffer-create.html
-rw-r--r-- 1 rostedt rostedt 23697 Jan 9 10:49 libtraceevent-parse_event.html
-rw-r--r-- 1 rostedt rostedt 23958 Jan 9 10:49 libtraceevent-event_get.html
-rw-r--r-- 1 rostedt rostedt 26292 Jan 9 10:49 libtraceevent-record_parse.html
-rw-r--r-- 1 rostedt rostedt 42977 Jan 9 10:49 libtraceevent-kbuffer-timestamp.html
-rw-r--r-- 1 rostedt rostedt 22496 Jan 9 10:49 libtraceevent-strerror.html
-rw-r--r-- 1 rostedt rostedt 31737 Jan 9 10:49 libtraceevent-func_apis.html
-rw-r--r-- 1 rostedt rostedt 46054 Jan 9 10:49 libtraceevent-kbuffer-read.html
-rw-r--r-- 1 rostedt rostedt 29118 Jan 9 10:49 libtraceevent-func_find.html
-rw-r--r-- 1 rostedt rostedt 28187 Jan 9 10:49 libtraceevent-plugins.html
-rw-r--r-- 1 rostedt rostedt 28611 Jan 9 10:49 libtraceevent-field_print.html
-rw-r--r-- 1 rostedt rostedt 22167 Jan 9 10:49 libtraceevent-file_endian.html
-rw-r--r-- 1 rostedt rostedt 25399 Jan 9 10:49 libtraceevent-fields.html
-rw-r--r-- 1 rostedt rostedt 21357 Jan 9 10:49 libtraceevent-long_size.html
-rw-r--r-- 1 rostedt rostedt 25549 Jan 9 10:49 libtraceevent-event_print.html
-rw-r--r-- 1 rostedt rostedt 21348 Jan 9 10:49 libtraceevent-log.html
-rw-r--r-- 1 rostedt rostedt 23701 Jan 9 10:49 libtraceevent-debug.html
-rw-r--r-- 1 rostedt rostedt 22353 Jan 9 10:49 libtraceevent-parse_head.html
-rw-r--r-- 1 rostedt rostedt 23027 Jan 9 10:49 libtraceevent-field_read.html
-rw-r--r-- 1 rostedt rostedt 28251 Jan 9 10:49 libtraceevent-field_get_val.html
-rw-r--r-- 1 rostedt rostedt 29720 Jan 9 10:49 libtraceevent-commands.html
-rw-r--r-- 1 rostedt rostedt 30686 Jan 9 10:49 libtraceevent-reg_print_func.html
-rw-r--r-- 1 rostedt rostedt 27448 Jan 9 10:49 libtraceevent-field_find.html
Is the html files suppose to be there?
-- Steve
next prev parent reply other threads:[~2023-01-09 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 12:11 [PATCH v6] libtraceevent: Add initial support for meson Daniel Wagner
2023-01-09 15:56 ` Steven Rostedt [this message]
2023-01-09 16:36 ` Daniel Wagner
2023-01-09 16:42 ` Steven Rostedt
2023-01-09 17:15 ` 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=20230109105616.168057c3@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).