tree 1466101d6fa42cbbda5d7af2e8c36f6d71ce16fb
parent 1b8cb739e0296395c9e0b6b9d16c7b6d676f6940
author Piotr Sikora <piotrsikora@google.com> 1646838579 -0600
committer GitHub <noreply@github.com> 1646838579 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiKMMzCRBK7hj4Ov3rIwAAQ+sIABDWC2oi83HRQjtomXga+NHl
 Vze2Z7BxbpYS/6+cFz0wc8wF20YnvNgJd0MZ0mAcDcrpjO87Utqf76sVrW2oucf/
 KGTFUkLDaQ3WCGYMgamPukliwLKWObyXlCr5hb2eH3/G5IeAW2MiudyBI6F4kjnd
 4Muczg9AHE2XyjoeVnsLY8DiidGxMOfJA1s1Du9HFNj900OSz6zxqyU4k43L5gB/
 YdWJWdmkwKgLBQEvHZVVZhJaq9pQqN08fQW4Vr7oQP4QLTcX3Pf69b1qasQF1CmF
 DcPclg9ek7h0X8nhD5cjkfpe2OCvnGZ6q/LHwXcdwmWLrEXCs42U+FVJ5uCxnfU=
 =YvHF
 -----END PGP SIGNATURE-----
 

Provide "executable" in wasm_cc_binary's DefaultInfo. (#998)

This is needed to allow custom rules and/or transitions on top of wasm_cc_binary (e.g. to workaround #972).

It's debatable whether .wasm is the correct executable target for non-standalone Wasm builds, but we don't have a way to differentiate those in wasm_cc_binary, and considering that this attribute isn't exported now, it shouldn't break anything.