-
-
Notifications
You must be signed in to change notification settings - Fork 779
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
在vs2022环境下面使用package.tools.cmake的生成的命令无法正确编译 #5230
Comments
Title: The command generated using package.tools.cmake under the vs2022 environment cannot be compiled correctly. |
由于是早上上班之前匆忙写的issue,没有发现已经有老外开了。 |
Since I wrote the issue in a hurry before going to work in the morning, I didn’t find that a foreigner had already opened it. |
需要同步 xmake 的配置,外面有可能会 也就是说,如果用户没用最新 cmake 版本,或者 cmake 没有及时更新适配。。即使 xmake 不传 toolset ,cmake 里面照样得跪,传了,反而不仅能同步 xmake 所有配置,还是保证即使 cmake 是低版本,也照样没这问题。。只要你保证 xmake 版本最新。 |
It is necessary to synchronize the configuration of xmake. It is possible to use In other words, if the user is not using the latest cmake version, or cmake is not updated and adapted in time. . Even if xmake does not pass the toolset, cmake still has to kneel down and pass it. On the contrary, it can not only synchronize all xmake configurations, but also ensure that cmake is a lower version, and there will still be no such problem. . As long as you keep the xmake version up to date. |
了解,我知道你的顾忌之处了。我自己先捣鼓一会吧 |
Got it, I understand your concerns. I'll tinker with it myself for a while. |
Xmake Version
2.9.2
Operating System Version and Architecture
Windows 11 家庭版 23H32
Describe Bug
在vs2022环境下面使用package.tools.cmake生成的命令无法正确编译
Expected Behavior
通过xmake调用cmake编译,具体来说是wxwidgets。
在vs2022下面出现奇怪的错误。
考虑到,我已经在同样的环境下面使用cmake事先编译过了。大概问题出在不同的cmake参数上?
我自己直接调用cmake的参数为:
这个命令行通过vs的命令行环境是能够直接执行的。
但是xmake生成的命令行多了很多东西,直接复制xmake生成的命令行一样不能正常构建。确切说就在于
这句。然后,现在最新的vs也只是143,这个v144哪来的?
使用v143是能够成功编译的
另外,xmake编译过程中出现了乱码,但是同样vs的命令行下,直接调用cmake是正确的显示。
Project Configuration
Additional Information and Error Logs
The text was updated successfully, but these errors were encountered: