While the example looks nice, it is horrible. They don't use #include "header.h", because includes don't work in their build. (Can't find the file, because we're too stupid to chdir / or too stupid to include the directory.)
Let's see. The python setup.py sdist bdist_wheel is made up. That command doesn't exist in setup.
I did figure out that the name of the output from cffi is defined in the ffi.set_source("_jamlib", section. Then you can from ._jamlib import ffi, lib, that is, if you get ever get the package built.
So I was able to get one thing from the example: How to name the final output package.
While the example looks nice, it is horrible. They don't use #include "header.h", because includes don't work in their build. (Can't find the file, because we're too stupid to chdir / or too stupid to include the directory.)
Let's see. The ```python setup.py sdist bdist_wheel``` is made up. That command doesn't exist in setup.
I did figure out that the name of the output from cffi is defined in the ```ffi.set_source("_jamlib",``` section. Then you can ```from ._jamlib import ffi, lib```, that is, if you get ever get the package built.
So I was able to get one thing from the example: How to name the final output package.
https://github.com/wolever/python-cffi-example This looks like it will help with cffi->wheel part.
While the example looks nice, it is horrible. They don't use #include "header.h", because includes don't work in their build. (Can't find the file, because we're too stupid to chdir / or too stupid to include the directory.)
Let's see. The
python setup.py sdist bdist_wheelis made up. That command doesn't exist in setup.I did figure out that the name of the output from cffi is defined in the
ffi.set_source("_jamlib",section. Then you canfrom ._jamlib import ffi, lib, that is, if you get ever get the package built.So I was able to get one thing from the example: How to name the final output package.