The cocos new command is behaving strange for me with 3.14, but it seems like it’s only being strange when I attempt to create a new project with precompiled libraries (the -t binary option). For whatever reason, it’s assuming Cocos2d-x v3.14 is installed in the same directory as the Cocos app I downloaded and installed a while ago. Here’s what I’m seeing:
My environment variables, set by setup.py:
My header search paths (in XCode build settings):
There is no cocos2d-x-3.14 directory in the Applications/Cocos directory, that’s not where I installed 3.14. This obviously leads to compilation errors (it can’t find cocos2d.h). I’ve searched all of my environment variables, nothing is pointing to /Applications/Cocos, so I’m not sure where that’s coming from. Also, I ran the setup.py program from v3.14 and sourced my bash_profile file before building the building the precompiled libraries template, and the cocos gen-libs command output my static libraries in the COCOS_X_ROOT directory. I’m at a loss as to what’s going on here. Sure, this seems like an easy fix to do (go in an modify the header searched paths and linked library paths) but I’d prefer to find a proper solution.