-
Notifications
You must be signed in to change notification settings - Fork 50
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
Swift C++ interoperability #20
Comments
No idea why. I didn’t know Swift 5.9 existed. Is this a pre-release?
Do you know why this is happening?
…On Thu, 20 Jul 2023 at 09:10, Arthur Guiot ***@***.***> wrote:
secp256k1 is not working when C++/ObjectiveC++ interoperability is
enabled with Swift 5.9.
[image: Capture d’écran 2023-07-20 à 10 09 34]
<https://user-images.githubusercontent.com/18022260/254817769-ff8a5c46-6495-44e0-9096-fa005492c5c9.png>
I get: Cannot find 'SECP256K1_CONTEXT_SIGN' in scope
—
Reply to this email directly, view it on GitHub
<#20>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACWUTTOKTDILAXALJSKK253XRDRV7ANCNFSM6AAAAAA2RBB2GU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Yes, it's a pre-release actually. Things works well when C++ interoperability is disabled. But when enabled, things starts to get weird... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
secp256k1
is not working when C++/ObjectiveC++ interoperability is enabled with Swift 5.9.I get:
Cannot find 'SECP256K1_CONTEXT_SIGN' in scope
The text was updated successfully, but these errors were encountered: