#6 Clean up build process(es)

Öppen
öppnade 4 år sedan av stevet · 2 kommentarer
  • Build jamlib
  • Static ansilove (if possible)
  • Make jamlib_build cleaner
  • cffi (let's make a wheel)? (groan)
  • Smaller docker image
* Build jamlib * Static ansilove (if possible) * Make jamlib_build cleaner * cffi (__let's make a wheel__)? (groan) * Smaller docker image
Steve Thielemann kommenterad 4 år sedan
Ägare

https://github.com/wolever/python-cffi-example This looks like it will help with cffi->wheel part.

https://github.com/wolever/python-cffi-example This looks like it will help with cffi->wheel part.
Steve Thielemann kommenterad 4 år sedan
Ägare

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.
Logga in för att delta i denna konversation.
Ingen Milsten
Ingen förvärvare
1 Deltagare
Laddar...
Avbryt
Spara
Det finns inget innehåll än.