On Wed, Mar 27, 2019 at 10:13:07AM +0100, Pierre Labastie via blfs-dev wrote:
>
> Note that for mesa -Db_ndebug=true can be used to disable assertions (the
> default is "if_release"). Then "-O2 -g" is still passed. You can also pass
> -Db_nebug=false with -Dbuildtype=release, of course...
To try to rephrase the question: Meson does things differently if
building for development or for release. I think that cmake is
similar, and for that we specify a release for at least some
packages.
Philosophically, if a package has been released, should we not make
a release build ?
Specifying no debug and a release build is of course redundant, as
your first sentence above notes. OTOH, distros often do specify
default options :)
If we do make a release build, I think some indication for our users
of how to debug it (if they need to) would be useful. That was why
I mentioned passing CFLAGS, CXXFLAGS to 'detune' it.
>
> BTW, using gdb with "-O2 -g" does not work well for me (I'm not a great user
> of gdb, so I might miss some option there): stepping gets confused if some
> part of the code gets optimized out, or reordered for optimization.
>
Same for me, but using a verbose build shows that those are the
values used for 'debugoptimized' in Mesa, which is how we are
currently building it.
ĸen
--
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/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
