OK, perfect.
Thanks
On Wed, Sep 3, 2014 at 10:21 AM, Joel Sherrill
wrote:
>
>
> On September 3, 2014 6:41:45 AM CDT, Federico Casares <
> federico.casa...@tallertechnologies.com> wrote:
> >Hi Joel,
> >
> >We did the lpc1768* BSPs. If we remove the NDEBUG... which will be the
> >procedure to di
On September 3, 2014 6:41:45 AM CDT, Federico Casares
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 b
On September 3, 2014 6:50:18 AM CDT, Sebastian Huber
wrote:
>On 03/09/14 13:41, Federico Casares wrote:
>>
>> We did the lpc1768* BSPs. If we remove the NDEBUG... which will be
>the
>> procedure to disable ASSERTS for production builds?
>
>Someone needs to add the magic to deal with NDEBUG in o
On 03/09/14 13:41, Federico Casares wrote:
We did the lpc1768* BSPs. If we remove the NDEBUG... which will be the
procedure to disable ASSERTS for production builds?
Someone needs to add the magic to deal with NDEBUG in our build system.
--
Sebastian Huber, embedded brains GmbH
Address : Dor
Hi Joel,
We did the lpc1768* BSPs. If we remove the NDEBUG... which will be the
procedure to disable ASSERTS for production builds?
regards.
On Tue, Sep 2, 2014 at 6:57 PM, Joel Sherrill
wrote:
> Hi
>
> The following BSPs define NDEBUG in their CFLAGS and thus fail
> to compile when RTEMS deb
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
