On 2016-05-31 10:12 AM, Dirkjan Ochtman wrote:
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 crate, which apparently needs dbus APIs that are not
easily available on this platform. The dbus crate is used through
servo -> net -> devices -> blurz -> dbus, i.e., for the Bluetooth DOM
APIs, which I'm pretty certain I won't need for this project anyway.
So I was wondering whether the project might accept a way of building
servo without Bluetooth support. Bringing this up in IRC, I was told
that this could be acceptable, but there was no agreement on the best
way to do it. The way that seems bothersome but straightforward was to
use feature daisy chaining; the alternative proposal was to have some
environment variable and add a build script somewhere that looks for
that variable.
What is the best way forward?
Doing it via Cargo features sounds like the better option to me. I'm
fine with enabling building Servo without bluetooth support.
Cheers,
Josh
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
