How to change COCOS2D_DEBUG value

[IzzyJM]

COCOS2D_DEBUG value is equal to ‘1’ in both debug and release builds for Android, and I think this will cause a lot of unnecessary code to be in my release build which I do not want. Is there a way to set this to ‘0’ or not define it like it does on iOS ? thanks for any feedback

more info:

COCOS2D_DEBUG in release builds

I have noticed that building the app in release mode (cocos run -p android -j 4 -m release) does in fact leave COCOS2D_DEBUG defined. This is a problem in my code because COCOS2D_DEBUG should only be defined for debug builds, to leave out test code etc from release builds… where can this be fixed? This behaviour of Android builds is also INCONSISTENT with iOS builds and should definitely be fixed. Here is something related: http://qiita.com/asuuma/items/7a7a21666272e7c44087

How to build an apk in in release mode from Android-Studio?

I’m trying to build an apk in release mode as I have few places in code with debug guards that I don’t want in release build. #if COCOS2D_DEBUG // something for debug only... #endif From terminal I invoke: cocos compile -p android -m release --android-studio (compiles successfully) but still resulted apk has debug code in it… What am I doing wrong?

[slackmoehrle]

@coulsonwang any thoughts?

[IzzyJM]

anyone could test it out write a statement like this and it will run the statement in both debug and release mode for android

if(COCOS2D_DEBUG == 1) {
// do something
}

[IzzyJM]

UPDATE: it is fixed in version 3.17.2 haven’t tested it but it should be according to this

Fix for COCOS2D_DEBUG is always 1 on Android

[slackmoehrle]

Let’s test it…

[IzzyJM]

I will test it out as soon as I figure out how to edit the .cmake file were you able to test it yet ?

[IzzyJM]

just curious does any one know what this code is actually doing different ? would like to know for more knowledge

[R101]

@IzzyJM Google would have helped with that

Here’s the info you’re after: CMake Generator Expressions

$<CONFIG:cfg>
    1 if config is cfg, else 0. This is a case-insensitive comparison. The mapping in 
    MAP_IMPORTED_CONFIG_<CONFIG> is also considered by this expression when
    it is evaluated on a property on an IMPORTED target.

[coulsonwang]

@IzzyJM already fixed here

[IzzyJM]

thanks alot thats what I was looking for but wasn’t exactly sure what to google just was wondering because the line that got changed looks alot similar to what it was before im trying to understand rightnow the meaning of the changes why the first one had quotes, guess I got some studing to do