From 3f758bcd3cfd8b20ef4437cf574d169ef35fd288 Mon Sep 17 00:00:00 2001 From: f321x Date: Tue, 27 Oct 2026 13:55:04 +0100 Subject: [PATCH] libsecp256k1: name the extrakeys and schnorrsig modules explicitly This is a no-op today: both modules have defaulted to yes in every secp256k1 release since 0.2.0. It only makes the dependency explicit, the way --enable-module-recovery already is, whose default is no. The dependency is real. coincurve links against the library this recipe installs rather than its own vendored copy, because its patch stubs out download_library() and _find_lib(), and its cffi build then includes secp256k1_extrakeys.h and secp256k1_schnorrsig.h unconditionally. secp256k1 installs those headers only for the modules that are enabled. Upstreamed from https://github.com/spesmilo/python-for-android --- pythonforandroid/recipes/libsecp256k1/__init__.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pythonforandroid/recipes/libsecp256k1/__init__.py b/pythonforandroid/recipes/libsecp256k1/__init__.py index f228ad8cb5..e5ee01a8f4 100644 --- a/pythonforandroid/recipes/libsecp256k1/__init__.py +++ b/pythonforandroid/recipes/libsecp256k1/__init__.py @@ -23,6 +23,8 @@ def build_arch(self, arch): '--prefix=' + self.ctx.get_python_install_dir(arch.arch), '--enable-shared', '--enable-module-recovery', + '--enable-module-extrakeys', + '--enable-module-schnorrsig', '--enable-experimental', '--enable-module-ecdh', _env=env)