You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm currently using Cocos2d-x version 3.0 on Mac OS 10.9 Mavericks.
When using the cocos run command in the Mac OS Terminal, no output (i.e. from CCLOG calls, with COCOS2D_DEBUG enabled) is sent to the console. However, if I open up my CocosTest.app package and run the binary directly from the Terminal, or if I build and run the project using Xcode, CCLOG output appears as expected. I think the issue has something to do with .app files swallowing output from stdout when opened from the Terminal, as opposed to directly running the binary.
Also, it'd be nice if cocos compile and cocos run automatically added a preprocessor flag for COCOS2D_DEBUG in debug mode! :)
The text was updated successfully, but these errors were encountered:
Hi! I'm currently using Cocos2d-x version 3.0 on Mac OS 10.9 Mavericks.
When using the
cocos run
command in the Mac OS Terminal, no output (i.e. fromCCLOG
calls, withCOCOS2D_DEBUG
enabled) is sent to the console. However, if I open up my CocosTest.app package and run the binary directly from the Terminal, or if I build and run the project using Xcode,CCLOG
output appears as expected. I think the issue has something to do with.app
files swallowing output fromstdout
when opened from the Terminal, as opposed to directly running the binary.Also, it'd be nice if
cocos compile
andcocos run
automatically added a preprocessor flag forCOCOS2D_DEBUG
in debug mode! :)The text was updated successfully, but these errors were encountered: