Skip to content

Update dependencies toward ring 0.17 and aarch64-pc-windows-msvc targeting support - #675

Closed
AArnott wants to merge 2 commits into
zingolabs:devfrom
nerdcash:depUpdates
Closed

Update dependencies toward ring 0.17 and aarch64-pc-windows-msvc targeting support#675
AArnott wants to merge 2 commits into
zingolabs:devfrom
nerdcash:depUpdates

Conversation

@AArnott

@AArnott AArnott commented Nov 12, 2023

Copy link
Copy Markdown
Contributor

These dependencies are in the tree that depend on ring 0.16.20 and prevent compiling for aarch64-pc-windows-msvc.
By updating them all these, the only remaining path to 0.16.20 is through hdwallet, which hasn't yet upgraded (jjyr/hdwallet#21).

This is one of several steps to upgrading the `ring` transitive dependency for native targeting of `aarch64-pc-windows-msvc`.
@AArnott

AArnott commented Nov 12, 2023

Copy link
Copy Markdown
Contributor Author

@juanky201271 Do you think you could help with addressing the build break:

error[E0433]: failed to resolve: use of undeclared crate or module `futures_core`
   --> /home/andrew/git/zingolib/target/debug/build/zingolib-acd9665e77faf7c5/out/cash.z.wallet.sdk.rpc.rs:711:35
    |
711 |         type GetBlockRangeStream: futures_core::Stream<
    |                                   ^^^^^^^^^^^^ use of undeclared crate or module `futures_core`

As this break is evidently in generated code instead of code within the repo (if I'm reading the path correctly), I don't know what it'll take to fix this.

@juanky201271

Copy link
Copy Markdown
Contributor

@juanky201271 Do you think you could help with addressing the build break:

error[E0433]: failed to resolve: use of undeclared crate or module `futures_core`
   --> /home/andrew/git/zingolib/target/debug/build/zingolib-acd9665e77faf7c5/out/cash.z.wallet.sdk.rpc.rs:711:35
    |
711 |         type GetBlockRangeStream: futures_core::Stream<
    |                                   ^^^^^^^^^^^^ use of undeclared crate or module `futures_core`

As this break is evidently in generated code instead of code within the repo (if I'm reading the path correctly), I don't know what it'll take to fix this.

Well, sorry, but I have no idea. Maybe @AloeareV can help up...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants