antocuni
commented
2 years ago This is a summary of what we do after merging #338 :
-
The final goal is to be able to write something like this
from setuptools import setup, Extension setup( name="hpy-simple-example", hpy_ext_modules=[ Extension('simple', sources=['simple.c')]), ], setup_requires=['hpy'], ) -
another requirement is to be able to build "universal modules": these require a different set of compilation options, and produces a file with a different extension:
simple.hpy.so. Currently, we do that by doingsetup.py --hpy-abi=universal build. -
we are using a setuptools entry point to detect
hpy_ext_modules=[...]and hook into setuptools:
- inside the hook, we automatically patch the distribution to use our own
build_hpy_extcommand forbuild_ext:
- this is where we modify the
Extensionto add the extra c files, include dirs, etc.:
On top of these, there are various hacks and bad monkey-patching to make things works. For example, we have to use this ugly hack to be able to distinguish hpy and normal extensions:
mattip
fangerer
This would simplify building projects that have migrated to HPy. This task would be something like