Build with libsecp256k1-haskell #41
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tochicool
force-pushed
the
libsecp256k1
branch
from
2cf0de7 to
5e4fdcf
Compare
tochicool
force-pushed
the
libsecp256k1
branch
from
5e4fdcf to
2d244ef
Compare
…nto libsecp256k1
tochicool
force-pushed
the
libsecp256k1
branch
from
171733f to
0cf9f73
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Building on #31 to get the two libraries to build with each other. I'm using these changes locally as I've needed some of the Schnorr bindings. I don't expect this to get merged and happy to close this once #31 is complete.
Related: libsecp256k1-haskell changes