> On Jun 23, 2015, at 10:14 AM, Raglan T. Tiger <[email protected]> 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 > Asserts do not get compiled into release code on windows. > > What are my options / setting for not compiling asserts into release builds?
First question: how are the asserts spelled? Different assert calls have different configuration. For example, the switch to disable assert() has no effect on NSAssert(). > Are these set in the Library project or the App project that links to them? Assert behavior is usually set when the library is compiled. Sometimes the library will have a runtime variable that affects assert behavior. -- Greg Parker [email protected] Runtime Wrangler _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
