cargo-build-system expects build dependencies to be in #:cargo-inputs, but the importer places them to #:cargo-development-inputs

  • Open
  • quality assurance status badge
Details
One participant
  • Valentin Ignatev
Owner
unassigned
Submitted by
Valentin Ignatev
Severity
normal
V
V
Valentin Ignatev wrote on 8 Jan 2020 18:27
(address . bug-guix@gnu.org)
CADXmXkghe3gw63APVEpQRUBpxoFx+aGhEbuX4b9LhUFYKeDTGA@mail.gmail.com
As the subject states, when you import a cargo package from crates.io,
importer places build dependencies to #:cargo-development-inputs, but
when you build the package, cargo fails to find such dependencies. It
works well if you move build deps from #:cargo-development-inputs to
#:cargo-inputs.

One example of this behavior is terminfo package and its phf-codegen
dependency. Another example is x11-dl package and its pkg-config
dependency

Regards,
Valentin
?