Skip to content
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

asio2库炸了? #5133

Closed
heheda123123 opened this issue Sep 4, 2024 · 4 comments · Fixed by #5135
Closed

asio2库炸了? #5133

heheda123123 opened this issue Sep 4, 2024 · 4 comments · Fixed by #5135
Labels

Comments

@heheda123123
Copy link
Contributor

Xmake 版本

v2.9.4+dev.c9c01c9b0

操作系统版本和架构

windows 11

描述问题

PS C:\Users\Administrator> xrepo info asio2
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.41.34120
The package info of project:
error: package(fmt/latest:{"header_only=false","runtimes=MT"}): conflict dependencies with package(fmt/latest:{"runtimes=MT"}) in asio2!
error: execv(C:\Users\Administrator\xmake\xmake.exe require --info --extra={system=false} asio2) failed(-1)

期待的结果

以前测试就是通过的,难道是依赖的库变了?

工程配置

不需要

附加信息和错误日志

已提供

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Title: asio2 library exploded?

@heheda123123
Copy link
Contributor Author

这是不是就和之前提到的问题一样,假如a包依赖b包的版本1包描述,但是b包更新到1.1包描述了,存在一些兼容问题造成a包无法编译,这时用户使用a包,依赖都是拉的最新的,即b包的1.1包描述,就炸了

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Is this the same as the problem mentioned before? If package a depends on the version 1 package description of package b, but package b is updated to the 1.1 package description, there are some compatibility issues that cause package a to fail to compile. In this case, the user uses package a , the dependencies are all the latest ones, that is, the 1.1 package description of package b, and it exploded.

@star-hengxing star-hengxing linked a pull request Sep 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@Issues-translate-bot @heheda123123 and others