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

Feature request: add possibility to separate dependency fetching and building steps #358

Closed
jauhien opened this issue Aug 9, 2014 · 5 comments
Labels
A-new-subcommand Area: new subcommand A-tooling Area: interaction with other tools

Comments

@jauhien
Copy link
Contributor

jauhien commented Aug 9, 2014

Please, add a possibility to separate these steps:

  • dependency fetching
  • dependency building
  • project building

It is may be not necessary when you are building your project by hand during development, but it is really needed in some automatic builds.

An example is ongoing integration of rust related stuff in Gentoo, where fetching and building phases should be separated even for packages that use git live versions, see https://github.com/Heather/gentoo-rust/issues/25

@sfackler
Copy link
Member

This'd also be nice to easily set up the dependency cache for offline development without having to go through a full build.

alexcrichton added a commit to alexcrichton/cargo that referenced this issue Sep 16, 2014
This command is used to download all dependencies of a package ahead of time to
ensure that no more network communication will be necessary as part of a build.

cc rust-lang#358
bors added a commit that referenced this issue Sep 16, 2014
This command is used to download all dependencies of a package ahead of time to
ensure that no more network communication will be necessary as part of a build.

cc #358
@SimonSapin
Copy link
Contributor

Is this fixed by #570?

@alexcrichton
Copy link
Member

Almost! I think this still needs to be able to separate building dependencies and building the main package itself. @jauhien, does that sound right?

@jauhien
Copy link
Contributor Author

jauhien commented Sep 22, 2014

@alexcrichton, it would be nice. Not critical for my usage though, but generally useful.

@alexcrichton alexcrichton added the A-new-subcommand Area: new subcommand label Oct 13, 2014
@alexcrichton alexcrichton added A-configuration Area: cargo config files and env vars A-tooling Area: interaction with other tools and removed A-configuration Area: cargo config files and env vars labels Jan 14, 2015
@alexcrichton
Copy link
Member

With cargo fetch plus cargo build -p I believe this is fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-new-subcommand Area: new subcommand A-tooling Area: interaction with other tools
Projects
None yet
Development

No branches or pull requests

4 participants