-
-
Notifications
You must be signed in to change notification settings - Fork 820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate configs packages are installed bug #6136
Comments
没懂啥问题? 这不是好好的么,不同配置,会有不同的 hash,要同时使用,就加 label + xmake/tests/projects/package/multiconfig/xmake.lua Lines 3 to 4 in 716b8e8
in xmake-repo:
-> zlib v1.3.1 [license:zlib]
-> zlib#1 v1.3.1 [toolchains:"clang", license:zlib]
please input: y (y/n/m) |
Don't understand any problem? Isn't this good? Different configurations will have different hashs. If you want to use them at the same time, add label + in xmake-repo:
-> zlib v1.3.1 [license:zlib]
-> zlib#1 v1.3.1 [toolchains:"clang", license:zlib]
please input: y (y/n/m) |
如果使用平台默认工具链 (msvc) 构建包后再显式指定 toolchains,会导致重新安装,但很明显编译器都是一样的。 有个想法就是,默认加上 |
目前设计是这样的,为了简化逻辑,目前仅根据 configs 变动算 buildhash。。否则逻辑太复杂。用户也搞不清楚。 反正除了一些不影响 build binary 的配置,其他只要 configs 变了,都会重装,即使编译器相同 |
If you use the platform default toolchains to build the package (msvc) and then specify toolchains explicitly, it will result in a reinstall, but it is obvious that the compiler is the same. One idea is that it might be better to add the |
The current design is like this. In order to simplify logic, the buildhash is currently calculated based on configs changes. . Otherwise the logic is too complicated. Users can't figure it out either. Anyway, except for some that do not affect the configuration of build binary, as long as configs change, they will be reinstalled, even if the compiler is the same |
Xmake Version
dev
Operating System Version and Architecture
Windows
Describe Bug
add_requires("zlib")
add_requires("zlib[toolchains=msvc]")
Expected Behavior
package
manifest.txt
should record compiler version?Project Configuration
Additional Information and Error Logs
N/A
The text was updated successfully, but these errors were encountered: