nimiq / core-rs

Official Rust implementation of the Nimiq protocol
https://nimiq.com
Other
74 stars 10 forks source link

No such file or directory (os error 2) nimiq-client #19

Closed animanga closed 5 years ago

jgraef commented 5 years ago

Can you give us more information? What command did you run? Is that the whole output?

I suspect it's because it can't find your configuration file.

animanga commented 5 years ago

yes i was running cargo run command in core rust than to me file not found when i changed toolchain again other error appearing ;) one minute i post

animanga commented 5 years ago
warning: function is never used: deserialize_string_vec --> client/src/serialization.rs:134:1 134 / pub(crate) fn deserialize_string_vec<'de, D, T>(deserializer: D) -> Result<Vec, D::Error> 135 where D: Deserializer<'de>, 136 T: FromStr, 137 T::Err: Display { 138 let values = Vec::::deserialize(deserializer)?; 139 values.iter().map( value T::from_str(value).map_err(Error::custom)).collect() 140 } _^
= note: #[warn(dead_code)] on by default

Finished dev [unoptimized + debuginfo] target(s) in 1m 25s
 Running `target/debug/nimiq-client`

No such file or directory (os error 2)

animanga commented 5 years ago

i am trying to build and run on Ubuntu 14.04LTS plus i changed toolchain to nightly

riptl commented 5 years ago

@animanga core-rs targets the nightly toolchain only. Make sure you add a configuration file before running the project: https://github.com/nimiq/core-rs#configuration

jgraef commented 5 years ago

You have to build with nightly. If you use rustup the easiest way is to override the toolchain in the core-rs directory:

rustup override set nightly

Alternatively tell cargo to use nightly:

cargo +nightly run

The issue with No such file or directory is because prior to our commits preparing for a beta release, the client looked for a config.toml in the current directory. But with the recent changes it will create an client.example.toml in $HOME/.nimiq when you first run it. You are then supposed to copy this to client.toml in the same directory and change the config to your needs.

The recent changes also updated the README, so that should be much clearer now. And the error message is much more descriptive now.

EDIT: Also that warning about deserialize_string_vec can be ignored.