> On Jun 23, 2015, at 17:24, Raglan T. Tiger wrote:
>
>> On Jun 23, 2015, at 5:48 PM, Scott Ribe wrote:
>>
>> Just to be clear, =1 is actually not necessary.
>
>
> Yes. But of course Xcode puts DEBUG=1 in the debug configuration.
>
> Just doing belt and suspenders.
>
> What if the compile
> On Jun 23, 2015, at 5:48 PM, Scott Ribe wrote:
>
> Just to be clear, =1 is actually not necessary.
Yes. But of course Xcode puts DEBUG=1 in the debug configuration.
Just doing belt and suspenders.
What if the compiler did
#ifdef NDEBUG
if ( NDEBUG == 1 )
#endif
Just sayin'.
-rags
__
On Jun 23, 2015, at 5:35 PM, Raglan T. Tiger wrote:
>
> I have added NDEBUG=1 in the project release configurationpre-processor macro
> definitions per results here.
Just to be clear, =1 is actually not necessary. The standard is that if NDEBUG
is defined, assert is turned off. It's just my pe
-rags
> On Jun 23, 2015, at 1:59 PM, Greg Parker wrote:
>
>
>> On Jun 23, 2015, at 10:14 AM, Raglan T. Tiger
>> wrote:
>>
>> My cocoa app links to a number of C++ BSD Static libraries. These libraries
>> are built in Release configuration. They have Asset Macros in them.
>>
>> The Asse
> On Jun 23, 2015, at 10:14 AM, Raglan T. Tiger wrote:
>
> My cocoa app links to a number of C++ BSD Static libraries. These libraries
> are built in Release configuration. They have Asset Macros in them.
>
> The Asserts are fired in the release builds. My Windows programmer tele that
> Ass
Define the preprocessor symbol NDEBUG, and assert( ) calls will be ignored.
It’s simplest to add this in the Build Settings under “Preprocessor Macros”,
only for the Release configuration.
—Jens
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
On Jun 23, 2015, at 11:14 AM, Raglan T. Tiger wrote:
>
> Are these set in the Library project or the App project that links to them?
It'll have to be the library; the app project has no influence over what is
compiled into the library.
As a guess, you might want to define NDEBUG=1. That is *ve
