Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump version to v1.0.0 #432

Merged
merged 8 commits into from
Nov 19, 2023
Merged

Bump version to v1.0.0 #432

merged 8 commits into from
Nov 19, 2023

Conversation

jgriffiths
Copy link
Contributor

@jgriffiths jgriffiths commented Nov 13, 2023

Hopefully the final set of changes to release v1.0.0

Depending on the environment variable WALLY_ABI_PY_WHEEL_USE_LIB:

 * If "no" or unset (or any unsupported value, with a warning), then the
   status quo is maintained: the libwally-core code will be (re)built
   as "amalgamated" objects that will then be linked into the Python
   extension.

 * If "static", then libwallycore.a and libsecp256k1.a will be built
   using the Autotools-based build system and will then be statically
   linked into the Python native extension library.

 * If "shared", then libwallycore.so (libwallycore.dylib on macOS) will
   be built using the Autotools-based build system and will then be
   dynamically linked into the Python native extension library. In this
   case, the Python extension will not contain any libwally-core or
   libsecp256k1 code, and the dynamic linker will need to find and load
   the libwallycore shared library (and, transitively, the libsecp256k1
   shared library) whenever the Python extension is loaded.
If the environment contains WALLY_ABI_PY_WHEEL_USE_PKG_SECP256K1=1 (and
the amalgamated objects are not being built), then the pkgconfig Python
module will be called to find the include path for the system-installed
libsecp256k1_zkp, and the secp256k1 submodule will not be checked out.

WALLY_ABI_PY_WHEEL_USE_PKG_SECP256K1 can alternatively be set to a
specific package name if the pkg-config name of the system-installed
libsecp256k1-zkp is something other than 'libsecp256k1_zkp'.
@jgriffiths jgriffiths force-pushed the build_updates branch 2 times, most recently from 1e6a4b0 to a60935b Compare November 19, 2023 18:56
@jgriffiths jgriffiths merged commit 6f67467 into master Nov 19, 2023
4 checks passed
@jgriffiths jgriffiths deleted the build_updates branch November 19, 2023 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants