Skip to content
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

Building issue (maybe due to use of Cargo workspace) #251

Closed
killkrt opened this issue Sep 8, 2016 · 2 comments · Fixed by #255
Closed

Building issue (maybe due to use of Cargo workspace) #251

killkrt opened this issue Sep 8, 2016 · 2 comments · Fixed by #255

Comments

@killkrt
Copy link

killkrt commented Sep 8, 2016

Hi,

I've noticed that the building process of this library is different from classic Rust libs or maybe (for sure ;-)) I'm doing something wrong.

When I run in the main folder:
cargo build

I get this error (with stable Rust 1.11.0):

error: failed to parse manifest at /home/killkrt/Development/vulkano/Cargo.toml

Caused by:
  no package or project section found.

And this error with nightly (1.13.0-923bac459):

error: manifest path `/home/killkrt/Development/vulkano/Cargo.toml` is a virtual manifest, but this command requires running against an actual package in this workspace

Anyway I was able to build each crate by myself going in each folder and launching cargo build.

As I understood cargo workspace are a new feature, but they should work with nightly release.
Anyway I think it should be mentioned in the README.mdthat you need a nightly version in order to build this lib and how.

Thank you.

@tomaka
Copy link
Member

tomaka commented Sep 8, 2016

Yes the crate is using workspaces.
The fact that you have to go in each directory is normal. The purpose of using a workspace is that all the crates share the same target directory.

tomaka added a commit that referenced this issue Sep 9, 2016
@killkrt
Copy link
Author

killkrt commented Sep 9, 2016

Thank you!

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

Successfully merging a pull request may close this issue.

2 participants