Differences between the meson build and autofoo
I just went through gvim $(find -name Makefile.\* -and -not -name Makefile.in -and -not -name Makefile.win32)
and here are my notes (well, I also ignored everything with win32
in its name that is still included by this find
):
-
all of perf/
is missing from meson-
(and that directory contains "generate a HTML report", written in perfectly readable autofoo; and for whatever reason it is important to have special support for running perf tests under valgrind
)
-
-
src/
has:-
check-def.sh
-
check-doc-syntax.sh
-
check-headers.sh
-
check-plt.sh
-
check-preprocessor-syntax.sh
-
plus some supporting infrastructure (a make target for cairo.def
?)
-
-
There are some check-doc-coverage.sh
andcheck-doc-syntax.sh
scripts mentioned in indoc/public/Makefile.am
-
There is lots of stuff in build/Makefile.am.gtk-doc
. Since I have neither clue about gtk-doc nor meson, I will just assume that meson deals with whatever that stuff is doing. -
build/Makefile.am.changelog
andbuild/Makefile.am.releasing
andbuild/Makefile.am.analysis
: Yeah, no, let's just get rid of that. Technically, this is missing from meson. -
There is something in test/Makefile.am
for summarising test suite runs. Lots ofsed
& friends. Does anyone use this? I also remember some Javascript-heavy HTML that showed the test results and made my browser freeze, but that apparently isn't in here...? -
test/
also has targets likecheck-ref-dup
andclean-ref-dup
andresults.tar.gz
that seem to do stuff with the test suite output. Checking for duplicates does sound a bit useful...?
So far, this is just a list of things I noticed. Feel free to edit this and say that some parts of this can just be dropped.