On Tue, 9 Apr 2019 at 13:54, Igor Gnatenko <ignatenkobr...@fedoraproject.org>
wrote:

> At this moment,
>
> * %meson doesn't pass -Db_ndebug at all, we use project-specific options
> * If project doesn't specify it, b_ndebug=false is default in meson
> * In case of mesa, it specifies b_ndebug=if-release which works correctly
> now with backported patch
>

IMO discussed here issue is more related to Fedora macros.

As current definition of the %meson uses --buildtype=plain
instead --buildtype=release and that build type is fixed and does not
provide any other way to redefine build type than just just pass
another --buildtype=<other_build_type> fiddling anything around plain build
profile straight in meson source code may introduce more harm than good
thing.

IMO whole rpm macro suite should proved something like %build_type macro
which should be used transparently by %configure, %cmake and %meson.
Effectively for now Fedora IMO needs only as %build_type something like
"release" and "debug".
Any other type of the build should have some strict definition of the
propose.

IMO it would be even good to have in whole rawhide development cycle
something like build all packages with build type "debug" and use "release"
type only after branching all packages and rebuild everything with build
type "release".
This would as well guarantee that whatever will be offered in new stable
release will be building with all other packages (which up to now still is
not the case).

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to