Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8] Reporter
	Description • 8 years ago

This will need to run rust-bindgen on JSAPI, build the sane Rust interface that wraps those generated definitions, build the rust-mozjs JS shell, and finally assert that this JS shell can successfully run js/src/Y.js.

We should probably generate + build + test both opt and debug, since historically getting rust bindings to JSAPI on both opt and debug has been a bit of pain.

This may also require getting rust-bindgen into tooltool or something. I expect further investigation will dig up new blockers.

	:Ms2ger (he/him; ⌚ UTC+1/+2)
	Comment 1 • 8 years ago

My initial idea was to build rust-bindgen within this task, but that requires a nightly rustc, which I don't believe we have on tooltool. Perhaps a bindgen binary is indeed the best idea.

Note that we need separate bindings per platform, due to C++ name mangling.

	Till Schneidereit [:till]
	Comment 2 • 8 years ago

I agree that a binary should be all we need. We don't compile any other build tools such as clang, after all :)

> Note that we need separate bindings per platform, due to C++ name mangling.

It might be possible to generate these from one generated set of bindings. The mangling is predictable per-platform, at least. mwu thought we should be able to do this, at least.

The advantage would be that we could bundle them up in one go, which seems quite a bit simpler than creating them per-platform and then collecting them later.

	Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8] Reporter
	Comment 3 • 8 years ago

Depends on https://github.com/servo/rust-bindgen/issues/16

	Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8] Reporter
	Comment 4 • 7 years ago

Doing this directly in bug 1277338.