On 27/02/17 19:57, Henri Sivonen wrote:
On Mon, Feb 27, 2017 at 5:57 PM, Henri Sivonen <hsivo...@hsivonen.fi> wrote:
Maybe having the header generation as part of build.rs is more trouble
than it's worth in the first place...
Now that the build.rs in commented out in the crates.io crate and the
generated header is shipped in the crates.io crate:
Considering that editing the vendored crates is not allowed, so I
can't put moz.build files on the path to the headers, what's the
appropriate way to make the m-c build system pick up headers from
third_party/rust/encoding_c/include?
I don’t know about the build system picking up part. For the restriction
on editing vendored code, one way to work around it with cooperation
from upstream is to use an optional cargo "feature":
http://doc.crates.io/manifest.html#the-features-section
The #[cfg(feature = "foo")] attribute and cfg!(feature = "foo") macro
are also available in build scripts.
--
Simon Sapin
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
