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

[Daniel Wagner <dwagner@suse.de>]

> > 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.

Right, in this case I should avoid breaking your working setup :) Anyway, let's
get first the initial setup working before doing fancy stuff.

> > > 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.

I've build the openSUSE packages using with Meson (just exchanged the build
instruction) and the tools didn't complain. So I think most of the problems
should be resolved. But experience tells me, there is always one bug more.

Daniel