Oh, interesting. I have had strange errors when not fully specifying the
features but the reason might have been something else.
We should just do that, then, agreed.
-Manish Goregaokar
On Tue, May 31, 2016 at 8:21 PM, Simon Sapin wrote:
> On 31/05/16 16:40, Manish
On 31/05/16 16:40, Manish Goregaokar wrote:
My main issue with cargo features is that they would pollute all the
Cargo.tomls in the dependency tree between servo and devices, and if
another dependency is added (even amongst these crates) it would have to be
added, or else we may get confusing
> It would be nice if you can "drop in" features from above without requiring
> daisy chaining, but AFAICT that's not always doable.
>
> It is possible currently to do `cargo build --features
> net/devices/nameoffeature` without polluting cargo.tomls, but IIRC this
> isn't always supposed to work
My main issue with cargo features is that they would pollute all the
Cargo.tomls in the dependency tree between servo and devices, and if
another dependency is added (even amongst these crates) it would have to be
added, or else we may get confusing compile errors.
It would be nice if you can
Hi all,
I'm investigating building a Servo-based headless browser (i.e. get
input events through the network, send PNGs out to the network).
Ideally, I'd like to get it to work on CentOS 6-based servers. Trying
to build server on one of these machines, I quickly ran into a problem
with the dbus
5 matches
Mail list logo