Open rakanalh opened 2 years ago
The polkadot crate should be renamed in some way I would suggest (or alternatively we can have our bin name different to the crate name - that would also fix it).
at least, polkadot-parachain
dependency in cumulus/polkadot-parachain/Cargo.toml
is not needed,
and is removed in this PR:
https://github.com/paritytech/cumulus/pull/1680/files#diff-5dcee2b3279312fb4434bec01df2816aeae5d1e593e2118b74706e1a2c905c83L72
and I am just wondering, if hack like with codec
deps, should work here also:
codec = { package = "parity-scale-codec", version = "3.0.0", default-features = false, features = ["derive"] }
so instead:
polkadot-parachain = { git = "https://github.com/paritytech/polkadot", default-features = false, features = [ "wasm-api" ], branch = "master" }
we use:
polkadot-parachain = { package = "polkadot-parachain-lib", git = "https://github.com/paritytech/polkadot", default-features = false, features = [ "wasm-api" ], branch = "master" }
When trying to compile cumulus from the root of the project like so (say branch :
The outcome would look as follows:
This is caused by the fact that the polkadot-parachain package defines it's name as such:
https://github.com/paritytech/cumulus/blob/95ca5a085727c1494ddeeae4a2b2e69c4ee1933b/polkadot-parachain/Cargo.toml#L1-L11
and also imports a crate with the same name: https://github.com/paritytech/cumulus/blob/95ca5a085727c1494ddeeae4a2b2e69c4ee1933b/polkadot-parachain/Cargo.toml#L72
This leads to confusion as to which one should be passed to
-p
CLI argument so that actual binary is built, without having to look at Cargo.toml