You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Use `pip install` instead of `setup.py install` in `recipe.py`
On Python 3.14, many recipes, notably `msgpack`, no longer byte-
compile with `setup.py install`, because the way that command
byte-compiles relies on `distutils`, which is gone.
* Import from setuptools and not distutils in the `android` recipe
* Remove freetype's distutils "fallback"
It was actually using distutils every time, apparently?
* Bump `freetype` version to match that of `freetype-py`
* On second thought, use the latest freetype version
* Use the latest *released* freetype-py version
* Tell setuptools what freetype-py version we have
* Turn `FreetypePyRecipe` into a `PyProjectRecipe`
I don't think this will require the version hack
* Put the `setuptools-scm` version hack back in
* Fix `FreetypePyRecipe.get_recipe_env`
* Switch to pythonhosted FreetypePy
`setuptools-scm` can't deal with the github hosted one, it seems.
* Update apsw recipe, use pythonhosted package
* Fix `LibffiRecipe.get_include_dirs` for `arch=None`
* Use recent libffi and cffi
* Require setuptools for every recipe
* `python`: update to `3.14.0`
* Use `pip install` instead of `setup.py install` in `recipe.py`
On Python 3.14, many recipes, notably `msgpack`, no longer byte-
compile with `setup.py install`, because the way that command
byte-compiles relies on `distutils`, which is gone.
* Import from setuptools and not distutils in the `android` recipe
* Remove freetype's distutils "fallback"
It was actually using distutils every time, apparently?
* Bump `freetype` version to match that of `freetype-py`
* On second thought, use the latest freetype version
* Use the latest *released* freetype-py version
* Tell setuptools what freetype-py version we have
* Turn `FreetypePyRecipe` into a `PyProjectRecipe`
I don't think this will require the version hack
* Put the `setuptools-scm` version hack back in
* Fix `FreetypePyRecipe.get_recipe_env`
* Switch to pythonhosted FreetypePy
`setuptools-scm` can't deal with the github hosted one, it seems.
* Update apsw recipe, use pythonhosted package
* Require setuptools for every recipe
* `python`: update to `3.14.0`
* Remove 'six' from `build_order` in `TestToolchainCL.test_create`
* Add 'six' to `python_modules` in `TestToolchainCL.test_create`
* Remove 'setuptools' from 'build_order' in `TestToolchainCL.test_create`
I guess because the hostpython already has it, there's no need to build it again?
* Revert the change to `modules_build_dir` in `Python3Recipe.create_python_bundle`
* Remove old versions from `modules_build_dir` expected value in `TestPython3Recipe.test_create_python_bundle`
* Roll back to an earlier apsw version
* only load libpython once
* fix pip install path
* fix build
* shift foundPython check
* fix newline
* remove unnecessary test
---------
Co-authored-by: Ansh Dadwal <[email protected]>
0 commit comments