xmake-repo VS Cocos2d

xmake [1] gives you something like this via `xrepo env shell`.

[1] https://xrepo.xmake.io/

This project should also soon be available on xrepo, right now you can copy the headers or use the package in `package.lua` to install.

Yes, although the documentation seems bare-bones, the code looks clean.

The xmake package repository files might be useful also for people interested in making their own package manager, or even installing by hand.

Here is the package information for autoconf, for instance:

https://github.com/xmake-io/xmake-repo/blob/master/packages/...

It has download links, checksums for specific versions, and the Lua syntax seems easy to parse.

The package for NanoVG however, does not indicate anywhere that you need the GLEW and GLFW libraries:

https://github.com/xmake-io/xmake-repo/blob/master/packages/...

Therefore, if the official xmake-repo repository already provides the required package, you can use it directly without specifying the package namespace.

I written a c/c++ package manager https://xrepo.xmake.io/#/

Currently, we have included the following toolchain packages in the xmake-repo repository, allowing xmake to pull and integrate remotely:

Here's the github page for xrepo: https://github.com/xmake-io/xmake-repo

That's all I can really tell you from what you've posted. The original version without the Blowfish encryption is open source (eg. https://github.com/cocos2d/cocos2d-x/blob/v4/cocos/scripting/lua-bindings/manual/CCLuaStack.cpp) , and I don't really understand how why you have so much symbol information available if what you're trying to disassemble isn't also probably open source

As others have pointed out, the biggest difference you're seeing is likely due to the _version_ of OpenGL (and hence GLSL) version. That said, there are still important differences. I'd recommend looking at a comparison between the same shader in a project that supports both OpenGL & OpenGLES. For example, here's a shader from cocos2d-x https://github.com/cocos2d/cocos2d-x/blob/v4/cocos/renderer/shaders/positionColor.vert. Note the only difference in this case is the additional precision qualifier (lowp) for v_fragmentColor. Note too how cocos uses preprocessor macros to handle this, so they don't have to maintain separate shader sources. Depending on your goals, you might be interested in tools like Nvidia cg or nvFX that allow for creating shaders in a dialect agnostic way, but ymmv.

Speaking about markdown files on GitHub, I know that there are some repositories that have very stunning README markdown files, such as this one for Cocos2d-x, whcih includes images in conjunction with text. I might do the same for my repository as well. Considering VS Code have an extension for .md files, this might come in handy when I consider using VS Code to contribute to my game projects.