xmake-repo
xmake-repo copied to clipboard
xmake-io
add acl-dev
这两个 acl 有什么区别 https://github.com/xmake-io/xmake-repo/blob/dev/packages/a/acl/xmake.lua
Bot detected the issue body's language is not English, translate it automatically.
What is the difference between these two acls? https://github.com/xmake-io/xmake-repo/blob/dev/packages/a/acl/xmake.lua
这两个 acl 有什么区别 https://github.com/xmake-io/xmake-repo/blob/dev/packages/a/acl/xmake.lua
之前的是一个老库，不知道干嘛的。这次加的acl库是国人开发的，一个后端开发框架，完全不一样 https://github.com/acl-dev/acl/blob/master/README_CN.md
Bot detected the issue body's language is not English, translate it automatically.
What is the difference between these two acls https://github.com/xmake-io/xmake-repo/blob/dev/packages/a/acl/xmake.lua
The previous one was an old library, I don’t know what it was used for. The acl library added this time was developed by Chinese people. It is a back-end development framework and is completely different. https://github.com/acl-dev/acl/blob/master/README_CN.md
昨天发现acl自带了xmake构建脚本，不过编译存在一些问题，等处理了，直接改为用xmake https://github.com/acl-dev/acl/issues/341
昨天发现acl自带了xmake构建脚本，不过编译存在一些问题，等处理了，直接改为用xmake acl-dev/acl#341
原来 add_patches 可以直接指定github上的链接，那还是挺方便的
Bot detected the issue body's language is not English, translate it automatically.
Yesterday, I discovered that acl comes with an xmake build script, but there are some problems with compilation. Once resolved, I directly changed to xmake [acl-dev/acl#341](https://github.com/acl-dev/acl/ issues/341)
It turns out that add_patches can directly specify the link on github, which is quite convenient.
昨天发现acl自带了xmake构建脚本，不过编译存在一些问题，等处理了，直接改为用xmake acl-dev/acl#341
原来 add_patches 可以直接指定github上的链接，那还是挺方便的
不过 github commit 的 patch ，它的 shasum 我记得有可能会变，一段时间后可能会 break。之前有人遇到过
