On Tue, Apr 14, 2015 at 3:12 PM, Emil Velikov wrote:
> On 14 April 2015 at 13:27, Marek Olšák wrote:
>> If --enable-debug is used, --enable-assertions is ignored.
>> --enable-assertions is basically a weaker version of --enable-debug.
>>
> Doesn't this make things more counter-intuitive ? I'm gui
On 14 April 2015 at 13:27, Marek Olšák wrote:
> If --enable-debug is used, --enable-assertions is ignored.
> --enable-assertions is basically a weaker version of --enable-debug.
>
Doesn't this make things more counter-intuitive ? I'm guilty of making
--enable-debug a bit messy (and I'm ok with rev
If --enable-debug is used, --enable-assertions is ignored.
--enable-assertions is basically a weaker version of --enable-debug.
There are 2 assert definitions in Mesa:
- The one that is enabled if DEBUG is defined (gallium only).
- The one that is enabled if NDEBUG is not defined (the standard ver
Hi Marek
On 13 April 2015 at 21:06, Marek Olšák wrote:
> From: Marek Olšák
>
> ---
> configure.ac | 11 ++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/configure.ac b/configure.ac
> index 6ccf3b4..f5eeb7d 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -402,
From: Marek Olšák
---
configure.ac | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 6ccf3b4..f5eeb7d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -402,6 +402,13 @@ AC_ARG_ENABLE([debug],
[enable_debug="$enableval"],
[e
