Existing build systems usually have some kind of installation targets that are used either manually (for installation in / usr / local or another place that the user can access), or automatically (build systems for packages from binary distributions or source package managers) .
What is the intended way to install software using Cargo? What should an analog look like make install?
Cargo itself uses an additional configure / make file that handles configuration, detection of system dependencies, startup cargo buildand installation.
Is this correct for any other software created with Cargo? Does this mean that it is planned to cover these tasks with Cargo itself or is Cargo intended only as a tool for collecting and compiling dependencies without any configuration / detection of installed deps / installation?
Or are you planning to add this functionality?
source
share