blockworks-foundation/mango-v4

error: failed to load manifest for workspace member `blockworks/mango-v4/bin/cli`

GildedHonour opened this issue · 6 comments

% cargo build
info: syncing channel updates for '1.65-x86_64-unknown-linux-gnu'
info: latest update on 2022-11-03, rust version 1.65.0 (897e37553 2022-11-02)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rust-docs'
info: downloading component 'rust-std'
info: downloading component 'rustc'
info: downloading component 'rustfmt'
info: installing component 'cargo'
info: installing component 'clippy'
info: installing component 'rust-docs'
info: installing component 'rust-std'
info: installing component 'rustc'
info: installing component 'rustfmt'

error: failed to load manifest for workspace member `blockworks/mango-v4/bin/cli`

Caused by:
  failed to load manifest for dependency `fixed`

Caused by:
  failed to read blockworks/mango-v4/3rdparty/fixed/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

Did you include the submodules when you cloned the repo? Perhaps git pull --recurse-submodules will help

@Lou-Kamades I did "git clone". At what point would I call git pull --recurse-submodules ?

% git clone ....
% cd <dir>

% git pull --recurse-submodules
Already up to date.

% cargo build
error: failed to load manifest for workspace member `blockworks/mango-v4/bin/cli`

Caused by:
  failed to load manifest for dependency `fixed`

Caused by:
  failed to read blockworks/mango-v4/3rdparty/fixed/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

what could be an issue? @ckamm

ckamm commented

Check if blockworks/mango-v4/3rdparty/fixed/Cargo.toml exists. If not, you didn't get the submodules. Something like git submodule update --init --recursive should do it.

I generally recommend setting the git setting "submodule.recurse=true" so you don't run into trouble like this as often.