Posting to lfs-dev because this seems to potentially affect all meson builds. In BLFS we already make release builds for cmake packages (i.e. without assertions), but I'm not sure 100% if we want to do that in LFS packages (I certainly do, for normal builds).
I'm starting to see indications that meson defaults to debug builds. This is prompted by https://www.phoronix.com/scan.php?page=news_item&px=Fedora-Mesa-Meson-Debug-Build which is specifically about Mesa. As always, views reported in comments there are not always reliable, My own build of 19.0.0 doesn't show what commands were actually used (I'm still looking to see how to make a verbose build), but so far I have the following points of interest: https://bugs.freedesktop.org/show_bug.cgi?id=109939#c16 In *Mesa* the default is -Dbuildtype=debugoptimized And from that thread, https://bugzilla.redhat.com/show_bug.cgi?id=1692426 Fedora have been using buildtype=plain which on current meson releases apparently does not remove the debug stuff. More on that in the phoronix link, -Db_ndebug=true apparently overrides it. On my own build of Mesa it noticed my CFLAGS (-O2 -march=native) but at the moment I have no idea if it even used them. There was also a comment that buildtype=release implies -O3 which might not be good for (binary) distros. The meson docs, which might be inaccurate on this, are at https://mesonbuild.com/Running-Meson.html ĸen, still looking to see if I can make verbose builds, but NOT giving any priority to this at the moment. -- It is said that there are two great unsolved problems in computer science: naming, cache invalidation, and off-by-one errors. -- Ben Bullock -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
