messense

Honestly I'm not sure what was your issue with it, it's working fine for me, https://github.com/Jake-Shadle/xwin/issues/141 is a flaky issue, it's not happening all the time, in fact it never...

> It is happening for me all the time Then please consider investing some time to help debugging the root cause of the issue.

See https://github.com/rust-cross/cargo-zigbuild/issues/164#issuecomment-1712791164

Should've been fixed by https://github.com/rust-cross/cargo-zigbuild/pull/273 which will be released in next version.

The fix was released in cargo-zigbuild [0.19.2](https://github.com/rust-cross/cargo-zigbuild/releases/tag/v0.19.2).

Do you have a reproducible example? Windows `.lib` files are usually static libraries or import libraries which are only used in compliation not in runtime, ~~so I'm not sure what...

This will require rebuilding all toolchains, it'd be nice to also upgrade GCC to 14.2.0.

The verbose log shows that you are actually building with pyo3 v0.23.1, have you tried upgrade it to at least 0.23.5 and ensure `python3-dll-a` is on latest version?

The `.lib` file is generated in pyo3 build script, so it's probably something wrong between `pyo3-build-config` and `python3-dll-a`, I'll transfer this issue to pyo3.

> Microsoft (R) Library Manager Version 14.29.30159.0 > Copyright (C) Microsoft Corporation. All rights reserved. > > Creating library C:\Users\Trim21\proj\uuid-utils\target\release\build\pyo3-ffi-db10177e3af506ff\out\lib\python3.lib and object C:\Users\Trim21\proj\uuid-utils\target\release\build\pyo3-ffi-db10177e3af506ff\out\lib\python3.exp from the verbose log, it's generating python3.lib...