luxolus
/
pyo3
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add section about linking in the guide

This commit is contained in:
konstin 2018-09-09 18:49:03 +02:00
parent d638a51971
commit 9405ffa3b9
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
build.rs
View File

@ -532,7 +532,7 @@ fn main() {
// TODO: Find out how we can set -undefined dynamic_lookup here (if this is possible)
}
let env_vars = ["LD_LIBRARY_PATH", "PATH", "PYTHON_SYS_EXECUTABLE"];
let env_vars = ["LD_LIBRARY_PATH", "PATH", "PYTHON_SYS_EXECUTABLE", "LIB"];
for var in env_vars.iter() {
println!("cargo:rerun-if-env-changed={}", var);

6
guide/src/debugging.md
View File

@ -1,5 +1,7 @@
# Debugging
## Macros
Pyo3's attributes, `#[pyclass]`, `#[pymodinit]`, etc. are [procedural macros](https://doc.rust-lang.org/unstable-book/language-features/proc-macro.html), which means that rewrite the source of the annotated item. You can view the generated source with the following command, which also expands a few other things:
```bash
@ -15,3 +17,7 @@ cargo rustc --profile=check -- -Z unstable-options --pretty=expanded -Z trace-ma
```
See [cargo expand](https://github.com/dtolnay/cargo-expand) for a more elaborate version of those commands.
## Linking
When building, you can set `PYTHON_SYS_EXECUTABLE` to the python interpreter that pyo3 should be linked to. You might need to set the `python2` or `python3` feature accordingly. On linux/mac you might have to change `LD_LIBRARY_PATH` to include libpython, while on windows you might need to set `LIB` to include `pythonxy.lib` (where x and y are major and minor version), which is normally either in the `libs` or `Lib` folder of a python installation. Also make sure that python is in `PATH` when you're not using `PYTHON_SYS_EXECUTABLE`.