Windows下Cargo build正常而xmake无法编译

[xixioba]

Xmake 版本

2.8.2+20230822

操作系统版本和架构

Win11 22621.2283

描述问题

参考官方教程在windows下构建了binary程序，Cargo build可以正常编译，但xmake编译提示
fatal error LNK1181: 无法打开输入文件“windows.0.48.5.lib”
xmake相比于官方教程仅仅添加了一些第三方库
Windows下使用了MSVC编译器，rustup default返回
stable-x86_64-pc-windows-msvc (default)

期待的结果

应该Windows/Macos/Linux下得到一致的执行文件

工程配置

compare_test.zip

附加信息和错误日志

[ 33%]: linking.release test.exe
rustc -C opt-level=3 --edition 2021 -L dependency=C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb927c8565450fa520f946fd3e0342\lib --extern chrono=C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb927c8565450fa520f946fd3e0342\lib\libchrono-90a3a9d5be5e1b32.rlib --extern clap=C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb927c8565450fa520f946fd3e0342\lib\libclap-f00337b08293c3d6.rlib --extern env_logger=C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb927c8565450fa520f946fd3e0342\lib\libenv_logger-8e05b27c5bd657e7.rlib --extern log=C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb927c8565450fa520f946fd3e0342\lib\liblog-b12108de843d5a68.rlib --crate-type=bin -o build\windows\x64\release\test.exe src\main.rs
error: @programdir\modules\private\async\runjobs.lua:256: @programdir\rules\rust\build\target.lua:67: @programdir\core\sandbox\modules\os.lua:273: error: linking with `link.exe` failed: exit code: 1181
***
***
***
 note: LINK : fatal error LNK1181: 无法打开输入文件“windows.0.48.5.lib”

[Issues-translate-bot]

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

---

Title: Cargo build is normal under Windows but xmake cannot compile

Xmake version

2.8.2+20230822

Operating system version and architecture

Win11 22621.2283

Describe the problem

Refer to Official Tutorial to build the binary program under windows. Cargo build can be compiled normally. But xmake compile prompts
fatal error LNK1181: Unable to open input file "windows.0.48.5.lib"
Compared with the official tutorial, xmake only adds some third-party libraries
The MSVC compiler is used under Windows, rustup default returns
stable-x86_64-pc-windows-msvc (default)

Expected results

You should get consistent executable files under Windows/Macos/Linux

Project configuration

compare_test.zip

Additional information and error logs

[33%]: linking.release test.exe
rustc -C opt-level=3 --edition 2021 -L dependency=C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb927c8565450fa520f946fd3e0342\lib --extern chrono=C:\compare_test\build\.packages\ c\cargo_test_deps\latest\abcb927c8565450fa520f946fd3e0342\lib\libchrono-90a3a9d5be5e1b32.rlib --extern clap=C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb927c8565450fa520f94 6fd3e0342\lib\libclap-f00337b08293c3d6.rlib --extern env_logger= C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb927c8565450fa520f946fd3e0342\lib\libenv_logger-8e05b27c5bd657e7.rlib --extern log=C:\compare_test\build\.packages\c\cargo_test_deps\latest\abcb9 27c8565450fa520f946fd3e0342\lib\ liblog-b12108de843d5a68.rlib --crate-type=bin -o build\windows\x64\release\test.exe src\main.rs
error: @programdir\modules\private\async\runjobs.lua:256: @programdir\rules\rust\build\target.lua:67: @programdir\core\sandbox\modules\os.lua:273: error: linking with `link.exe` failed: exit code: 1181
***
***
***
 note: LINK : fatal error LNK1181: Unable to open input file "windows.0.48.5.lib"

[xixioba]

经过对比cargo build，发现缺少了rustup\.cargo\registry\srclindex.crates.io里面的系统库链接

[Issues-translate-bot]

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

---

After comparing cargo build, it was found that the system library link in rustup\.cargolregistry\srclindex.crates.io is missing

[waruqi]

经过对比cargo build，发现缺少了rustup\.cargo\registry\srclindex.crates.io里面的系统库链接

关键是我还不清楚，这个路径怎么可靠的取出来

[Issues-translate-bot]

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

---

After comparing cargo build, it was found that the system library link in rustup\.cargo\registry\srclindex.crates.io is missing! [{C79082B3-B1E5-96AB-5FBF-1389D8F19DC8}](https://user -images.githubusercontent.com/34228625/269174057-ff92df38-9432-47f7-b3f5-b5988e5e4da9.png)

The key is that I still don’t know how to reliably extract this path.

[xixioba]

似乎已经能抓到这个依赖，但是传递给rustc的时候没了

顺便，我们可以只用xmake提取编译产物，cargo build取完成原生的工程编译么，因为发现xmake对cargo.toml的支持比较少，迁移到xmake.lua需要再写一遍，不是很优雅

[Issues-translate-bot]

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

---

It seems that this dependency has been caught, but it is gone when passed to rustc

By the way, can we only use xmake to extract the compilation products, and cargo build to complete the native project compilation? Because we found that xmake has less support for cargo.toml, migrating to xmake.lua requires writing it again, no very elegant

[waruqi]

似乎已经能抓到这个依赖，但是传递给rustc的时候没了

顺便，我们可以只用xmake提取编译产物，cargo build取完成原生的工程编译么，因为发现xmake对cargo.toml的支持比较少，迁移到xmake.lua需要再写一遍，不是很优雅

那你直接 on_build 通过 os.exec 执行下 cargo build，在 after_build 里面去下产物就行，其实用不用 xmake 也无所谓了。

xmake 里面支持 rust ，主要目的是为了跟 c++ 混编需要，纯粹的 rust 项目，直接走 cargo build ，完全没必要用 xmake

[Issues-translate-bot]

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

---

It seems that this dependency has been caught, but it is gone when passed to rustc

By the way, we can only use xmake to extract the compilation products, and cargo build to complete the native project compilation. Because we found that xmake has less support for cargo.toml, we need to write it again when migrating to xmake.lua. not very elegant

Then you can directly execute cargo build through on_build through os.exec, and download the product in after_build. In fact, it doesn’t matter whether you use xmake or not.

xmake supports rust. The main purpose is to mix it with c++. For pure rust projects, just use cargo build directly. There is no need to use xmake.

[xixioba]

那是后话了，现在的确是c++和rust混编的需求，macos/linux都搭完了，就剩windows下这个奇怪的问题了

[Issues-translate-bot]

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

---

That's a thing for another day. Now there is indeed a need for mixed compilation of C++ and Rust. Macos/Linux are all set up, and only this strange problem remains under Windows.

[waruqi]

那是后话了，现在的确是c++和rust混编的需求，macos/linux都搭完了，就剩windows下这个奇怪的问题了

暂时没时间细研究，得看下这个路径怎么可靠的取出来，只要能取到 这边加上对应 -L flags 就行了，你可以先分析下看看

[Issues-translate-bot]

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

---

That’s a story for another day. Now there is indeed a need for mixed compilation of C++ and Rust. Macos/Linux are all set up, leaving only this strange problem under Windows.

I don’t have time to study it in detail at the moment, so I have to see how to reliably retrieve this path. As long as it can be retrieved, just add the corresponding -L flags here. You can analyze it first.

[xixioba]

关联 #4552 ，使用cargo build来编译纯rust项目