On Wed, Jun 1, 2016 at 10:53 AM, Manish Goregaokar
wrote:
> It should be net/device/bluetooth. For some reason the crate is imported as
> "device" instead of "devices" in net
I'm somehow still running into trouble. Can someone spot the mistake?
djc@dochtman-dev servo $ cat ~/.cargo/config
paths
Hi,
While building Servo source on Ubuntu 15.10, servo-glutin failed because it
couldn't get wayland-client crate. Here is the output of "cargo build" executed
inside
servo/.cargo/registry/src/github.com-1ecc6299db9ec823/servo-glutin-0.4.16:
cargo build --verbose
Fresh libc v0.2.11
It seems like it's still checking the git repo for the feature. Might be
worth landing your devices changes and proceeding from there.
-Manish Goregaokar
On Thu, Jun 2, 2016 at 12:56 PM, Dirkjan Ochtman wrote:
> On Wed, Jun 1, 2016 at 10:53 AM, Manish Goregaokar
> wrote:
> > It should be net/d
On Thu, Jun 2, 2016 at 11:20 AM, Manish Goregaokar
wrote:
> It seems like it's still checking the git repo for the feature. Might be
> worth landing your devices changes and proceeding from there.
I've filed a Cargo bug:
https://github.com/rust-lang/cargo/issues/2762
And created a devices PR:
On 02/06/16 10:31, sow...@gmail.com wrote:
crate.io does show that wayland-client crate is available. Any idea
how to make build get this crate?
The package name (known by Cargo and crates.io) is wayland-client, it’s
the library name (known by rustc) that’s wayland_client.
https://crates.io/
Yes, earlier I thought it's was a typo with "extern crate wayland-client" but
looks like that's the correct way as "_" throws up immediate error.
I also tried using --verbose while compiling servo and the output is as follows:
[ snip ]
Compiling profile_traits v0.0.1
(file:///root/servo-modi
6 matches
Mail list logo