-
Notifications
You must be signed in to change notification settings - Fork 81
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
Unable to build the recent version according to the documentation #129
Comments
any update on this ? |
UPD: I've attempted to switch the library version to the altered I've switched to the [package]
name = "iroha_python"
version = "0.1.0"
authors = ["Iroha 2 team <https://github.com/orgs/soramitsu/teams/iroha2>"]
edition = "2021"
license-file = "LICENSE"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[workspace]
members = ["generate"]
[lib]
name = "iroha2"
crate-type = ["cdylib"]
[dependencies]
iroha_client = { git = "https://github.com/hyperledger/iroha", branch = "iroha2-dev" }
iroha_crypto = { git = "https://github.com/hyperledger/iroha", branch = "iroha2-dev" }
iroha_data_model = { git = "https://github.com/hyperledger/iroha", branch = "iroha2-dev" }
iroha_version = { git = "https://github.com/hyperledger/iroha", branch = "iroha2-dev" }
color-eyre = "0.6"
parity-scale-codec = "3.1"
pyo3 = { version = "0.16.4", features = ["extension-module", "multiple-pymethods"] }
pythonize = "0.16.0"
serde = "1"
serde_json = "1" Sadly, there's another build error that doesn't let this build to work.
|
Which commit are you guys trying to build? I just cloned the iroha2 branch and my version conflicts start from this:
And upon resolving this and following conflicts, I am stuck trying to solve the following conflict:
Making things worse, I am working on an ARM based system (M1). Any recommendations on making iroha-python work under my system? |
I did the following steps and worked for me: |
Today, @learningnoobi wrote that a fresh
qroha-python
is broken:I have also notified @QuentinI.
The text was updated successfully, but these errors were encountered: