BSPs which define NDEBUG in CFLAGS

[Joel Sherrill]

On September 3, 2014 6:41:45 AM CDT, Federico Casares <federico.casares at tallertechnologies.com> wrote:
>Hi Joel,
>
>We did the lpc1768* BSPs. If we remove the NDEBUG... which will be the
>procedure to disable ASSERTS for production builds?

Ultimately you (end user) select the flags you want to deploy with. :)

My goal is just ensure builds work with and without it defined.

>regards.
>
>
>
>On Tue, Sep 2, 2014 at 6:57 PM, Joel Sherrill
><joel.sherrill at oarcorp.com> wrote:
>
>Hi
>
>The following BSPs define NDEBUG in their CFLAGS and thus fail
>to compile when RTEMS debug is enabled:
>
>mvme136
>lpc1768_mbed_ahb_ram
>lpc1768_mbed
>rtl22xx
>
>I have tracked this down to newlib's assert.h (correctly) not
>defining __ASSERT_FUNC when NDEBUG is defined.  This trips
>up the RTEMS assert definitions which rely on that definition
>of __ASSERT_FUNC.
>
>I can fix this by using the logic in newlib's assert.h to define
>__RTEMS_ASSERT_FUNC for our own assert's use.
>
>Any objections to this approach?
>
>--
>Joel Sherrill, Ph.D.             Director of Research & Development
>joel.sherrill at OARcorp.com        On-Line Applications Research
>Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>Support Available                (256) 722-9985
>
>_______________________________________________
>devel mailing list
>devel at rtems.org
>http://lists.rtems.org/mailman/listinfo/devel
>
>
>
>
>-- 
>
> 
>Casares, Federico
>
>Sr. Software Engineer
>
>Taller Technologies Argentina
>
>San Lorenzo 47, 3rd Floor, Office 5
>Córdoba, Argentina