Re: [PATCH v5] libtracefs: Add initial support for meson

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: Thu, 5 Jan 2023 08:51:02 -0500	[thread overview]
Message-ID: <20230105085102.0a9c464b@gandalf.local.home> (raw)
In-Reply-To: <20230105071851.24okzoqun6ednbmr@carbon.lan>

On Thu, 5 Jan 2023 08:18:51 +0100
Daniel Wagner <dwagner@suse.de> wrote:

> On Wed, Jan 04, 2023 at 12:44:14PM -0500, Steven Rostedt wrote:
> > On Wed, 4 Jan 2023 18:19:39 +0100
> > Daniel Wagner <dwagner@suse.de> wrote:
>  > setup. Basically with  
> > > 
> > > 
> > >   'meson setup .build --wrap-mode=forcefallback'
> > > 
> > > in trace-cmd meson would download, setup and build libtraceevent and libtracefs
> > > within the trace-cmd build. This is makes the whole development process
> > > between these project way smoother. And if you would configure the build
> > > with  
> > 
> > I'm not sure that would make it easier for me. I work on each separately.
> > And I don't always want them linked together, but sometimes I do!  
> 
> Meson doesn't force you here how you prefer you workflow. If you want to
> stick with your development steps all should be fine. I just recommend to give
> those subproject a try. IMO it makes things simpler, e.g. building all code in
> debug mode and being able to single step through is nice. And if you find a bug
> or want to change a line in the libraries, just change the line recompile the
> main project and that's all. No installing or fiddling with some $PATHs. All works
> out of the box.

I get that now with my current setup. I only install with debug options,
and use gdb in emacs. It walks through the library code, and will go into
different paths automatically. I only need to install the code I change
(sure, I need to go into that path to do so). But as I've been using
libtracefs and libtraceevent for other tooling, I really don't want it part
of the trace-cmd repo, or in the build path.

> 
> > For the environment that we require a static build, that isn't really
> > needed. It would only make the initial setup easier, but that's a one time
> > deal. After that, everything is automated.  
> 
> Before you spend too much time in writing scripts aroudn Meson, you should
> really have a look at subproject. You get the dependencies management for little
> costs.

The above mentioned static environment build is done via portage.

-- Steve