On Tue, Dec 20, 2022 at 07:08:40PM +0100, Daniel Wagner wrote: > Introduce Meson as build framework for building libtraceevent. This > lives besides the Makefiles until all the expected initial fallouts > have been dealed with. > > The build steps are: > > # configure using .build as build directory and install destination > # /tmp/test > meson --prefix=/tmp/libtraceevent .build > > # trigger the build > ninja -C .build > > # install the library > ninja -C .build install > > In case you want to build/install the documentation the setup is > > meson -Ddocs-build=true .build > > Signed-off-by: Daniel Wagner <dwagner@xxxxxxx> > --- > v4: > - install man pages to correct section, in this case 3 During my packaging attempt I found out that the man pages are installed into subdirs. So I started to look into the this and ... let's say it's complicated. For example libtraceevent-func_apis.txt list a few function which are also listed in libtraceevent-func_find.txt. The Makefile uses these function as build names but, if we have two targets with the same name one will overwrite the other. make seems to tolerate something like this. Meson doesn't. I am playing with various ideas how we could handle this. Currently, I think the best way is to distinguish the different source txt files. So we have files which are for generating a mans per function (1:n) and we have txt files which are general documentation (1:1).
|