#define NSLog (...) still print output to the console

Question

I tried to disable NSLog in release build.

I put the following code in .pch file

#ifndef __OPTIMIZE__
# define NSLog(...) NSLog(__VA_ARGS__)
#else
# define NSLog(...) {}
#endif

It's not working, so I tried

# define NSLog(...) {}

It still prints output to the console.

Any help will be good, thanks!

You should probably switch on `NDEBUG`, and not `__OPTIMIZE__`. — jww, Jan 23 '15 at 17:09

score 1 · Answer 1 · answered Mar 31 '11 at 20:10

you would declare your own log function and use that instead. its implementation could go through NSLogv, if you want a va list. its implementation would also not forward the messages to NSLogv when disabled, so you will likely need more than one flavor of logger.

score 1 · Answer 2 · edited May 23 '17 at 11:58

1

Sounds like what you want is similar to this definition for DLog from this previous SO answer on NSLog tips and tricks.

#ifdef DEBUG 
#   define DLog(fmt, ...) NSLog((@"%s [Line %d] " fmt), __PRETTY_FUNCTION__, __LINE__, ##__VA_ARGS__); 
#else 
#   define DLog(...)
#endif

edited May 23 '17 at 11:58

Community

1
1

answered Mar 31 '11 at 21:03

progrmr

73,806
16
109
147

score 0 · Answer 3 · answered Feb 01 '13 at 08:56

0

Preprocessor macro set in Build Setting of project having: DEBUG=1 $(inherited)

So now just use : if(DEBUG) NSLog(@"Your log");

answered Feb 01 '13 at 08:56

Sandip Patel - SM

3,276
26
27

score 0 · Answer 4 · answered Sep 02 '15 at 20:43

0

In you application .pch file put following line. define NSLog(dese,...)

It will stop printing.

answered Sep 02 '15 at 20:43

John Smith

134
10

Joe · Answer 5 · 2011-03-31T20:59:49.143

0

Make sure __OPTIMIZE__ is defined in the build settings or higher up in the .pch file itself and that the pch file is set in the Prefix Header (GCC_PREFIX_HEADER) Build Settings. Also you can define NSLog(...) as nothing

#define NSLog(...)

edited Mar 31 '11 at 20:59

answered Mar 31 '11 at 19:57

Joe

56,349
8
124
132

Probably not best to define it out as nothing - this can cause unintended side effects in code, e.g., an if statement with a single NSLog following and no brackets... – fbrereto Mar 31 '11 at 20:02
1

Although I said good point I just realized that you still need a semicolon after the NSLog so `for(int i = 0; i< 10; i++);` is valid. Where it could cause an issue is using a comma in code. `int i;i=10,NSLog("i %d", i);` – Joe Mar 31 '11 at 20:21
{} do not work with the comma operator either o.O `i=10,{};` = !Expected expression. – Joe Mar 31 '11 at 20:58

#define NSLog (...) still print output to the console

5 Answers5