commit
39edeebf67
|
@ -187,7 +187,7 @@ This happens on Windows when linking to the python DLL fails or the wrong one is
|
|||
- `python3X.dll` for Python 3.X, e.g. `python310.dll` for Python 3.10
|
||||
- `python3.dll` when using PyO3's `abi3` feature
|
||||
|
||||
The DLL needs to be locatable using the [Windows DLL search order](https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order#standard-search-order-for-unpackaged-apps). The two easiest ways to achieve this are:
|
||||
The DLL needs to be locatable using the [Windows DLL search order](https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order#standard-search-order-for-unpackaged-apps). Some ways to achieve this are:
|
||||
- Put the Python DLL in the same folder as your build artifacts
|
||||
- Add the directory containing the Python DLL to your `PATH` environment variable, for example `C:\Users\<You>\AppData\Local\Programs\Python\Python310`
|
||||
- If this happens when you are *distributing* your program, consider using [PyOxidizer](https://github.com/indygreg/PyOxidizer) to package it with your binary.
|
||||
|
|
Loading…
Reference in a new issue