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

Do not include libsecp256k1 on Windows #1069

Merged
merged 2 commits into from
Dec 8, 2021

Conversation

cmichi
Copy link
Collaborator

@cmichi cmichi commented Dec 7, 2021

Fixes the broken cargo-contract Windows CI. See #1068 for more details.

CI fails due to expected incompatible ink! with substrate-contracts-node since the deposit PR merge.

Copy link
Contributor

@HCastano HCastano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this is the error message a user on Windows would get if they tried to use to_eth_address:

error[E0599]: no method named `to_eth_address` found for struct `ECDSAPublicKey` in the current scope
  --> lib.rs:29:28
   |
29 |             let addr = key.to_eth_address();
   |                            ^^^^^^^^^^^^^^ method not found in `ECDSAPublicKey`

For more information about this error, try `rustc --explain E0599`.

I wonder if we can have a cfg_if check and panic with a better message instead

Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
@HCastano HCastano merged commit 7a4307f into master Dec 8, 2021
@HCastano HCastano deleted the cmichi-do-not-include-libsecp256k1-on-windows branch December 8, 2021 22:47
xgreenx pushed a commit to Supercolony-net/ink that referenced this pull request Feb 8, 2022
* Do not include `libsecp256k1` on Windows

* Apply suggestions from code review

Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>

Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
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