From: Daniel Wagner <dwagner@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v5] libtraceevent: Add initial support for meson
Date: Thu, 5 Jan 2023 08:05:31 +0100 [thread overview]
Message-ID: <20230105070531.p5z6czgflrljrnpq@carbon.lan> (raw)
In-Reply-To: <20230104123456.70202ea9@gandalf.local.home>
On Wed, Jan 04, 2023 at 12:34:56PM -0500, Steven Rostedt wrote:
> On Wed, 4 Jan 2023 12:31:43 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Wed, 4 Jan 2023 18:05:59 +0100
> > Daniel Wagner <dwagner@suse.de> wrote:
> >
> > > > It's still missing the building of the static library libtraceevent.a.
> > >
> > > This is controlled via 'meson setup --default-library {shared, static, both}'.
> >
> > Can we make it default to 'both' ?
>
> Actually, I'm working on adding a Makefile that controls all this. I can
> make that do the "both"
Sure, the defaults are controlled via the project() command:
project(
'libtraceevent', ['c'],
meson_version: '>= 0.50.0',
license: 'LGPL-2.1',
version: '1.7.0',
default_options: [
'c_std=gnu99',
'buildtype=debug',
'default_library=both',
'prefix=/usr/local',
'warning_level=1',
]
)
next prev parent reply other threads:[~2023-01-05 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 8:29 [PATCH v5] libtraceevent: Add initial support for meson Daniel Wagner
2023-01-04 15:45 ` Steven Rostedt
2023-01-04 17:05 ` Daniel Wagner
2023-01-04 17:31 ` Steven Rostedt
2023-01-04 17:34 ` Steven Rostedt
2023-01-05 7:05 ` Daniel Wagner [this message]
2023-01-04 16:01 ` Steven Rostedt
2023-01-04 17:10 ` Daniel Wagner
2023-01-04 17:32 ` Steven Rostedt
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=20230105070531.p5z6czgflrljrnpq@carbon.lan \
--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).