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

[Steven Rostedt <rostedt@goodmis.org>]

On Wed, 4 Jan 2023 18:19:39 +0100
Daniel Wagner <dwagner@suse.de> wrote:

> On Wed, Jan 04, 2023 at 11:09:16AM -0500, Steven Rostedt wrote:
>  This also doesn't build the static library libtracefs.a.
> > 
> > We have environments that we need to build trace-cmd statically. As
> > trace-cmd depends on libtraceevent and libtracefs, that means both need a
> > static library as well.  
> 
> Configure the build with
> 
>   'meson setup .build --default-library=both'
> 
> Though, we could add libtraceevent and libracefs as subprojects to trace-cmd
> which avoids all the hassle to install libtraceevent and libtracefs
> independenly from trace-cmd. It also takes care of all the dependency
> 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! To
control what gets linked to trace-cmd, I use dynamic libraries, and only
install what I want to use there. That is, they really are three different
projects! I use libtracefs on several other tools, not just trace-cmd.

> 
>   'meson setup .build --wrap-mode=forcefallback --default-library=static'
> 
> would staticly link all subprojects into the trace-cmd binary.
> 
> I haven't added this part to the initial mesonizing of the projects. Keep
> things simple to begin with.

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.

-- Steve