Re: Howto supply cargo-build-system dependency to guix package definition

[Timothy Washington <twashing@gmail.com>]

Ok nice. I got much further with the rust-anyhow definition here
<https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/crates-io.scm#n2773>
(in crates-io).

With these arguments..

   (arguments
    `(#:cargo-inputs
      (("rust-ansi-term" ,rust-ansi-term-0.12)
       ("rust-anyhow" ,rust-anyhow-1))))


..the build fails on missing "cidr-utils". Now "cidr-utils" is in Rust's
crates.io <https://crates.io/crates/cidr-utils>.
But is that what Guix' cargo-build-system is referencing?
Otherwise, do we need to create a Guix .scm (scheme definition)?

starting phase `build'
error: no matching package found
searched package name: `cidr-utils`
perhaps you meant:      pin-utils
location searched: registry `crates-io`
required by package `rustscan v2.1.1
(/tmp/guix-build-rustscan-2.1.1.drv-0/source)`
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "cargo" arguments: ("build"
"--release") exit-status: 101 term-signal: #f stop-signal: #f>



Tim


On Thu, 27 Apr 2023 at 12:37, ( <paren@disroot.org> wrote:

> Timothy Washington <twashing@gmail.com> writes:
> >  starting phase `build'
> >  error: no matching package named `anyhow` found
> >  location searched: registry `crates-io`
> >  required by package `rustscan v2.1.1
> (/tmp/guix-build-rustscan-2.1.1.drv-0/source)`
>
> Just add the input to the #:CARGO-INPUTS:
>
> ```
> `(...
>   (("rust-anyhow" ,rust-anyhow-2)))
> ```
>
> Make sure to keep the inputs in alphabetical order :)
>