tree 3c27a42af9d10ce6b3b90ffc3c0707d376cbc45d
parent 612f4362bc2b5d9aa7d9307ecaf3346faba285af
author David Tolnay <dtolnay@gmail.com> 1650991016 -0700
committer GitHub <noreply@github.com> 1650991016 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiaB+oCRBK7hj4Ov3rIwAAOjAIAG72NVkycRDnzOmwNyKYWdD/
 3rZG2s+hTaDesGGft4VRigAr3yCulnAIEPZPR/eELzKL9VcogGpzfadrqmzFf3E5
 qd/MbPs7qsb6rxvLeYYhH//9vyD8e3zEW2Y3X3Ljm5bWKSVbrbfikcc9dKZsuQ+K
 myPNkQ/hqg3YksCicg3cZD9e6GYpMLuA6ETYZBJhdz3vT92K26XjJYNBsjguEgON
 940fvLd1WKFDOs84OEBcz497C0zSp7RZblxRxherljJf6J55bv6svOdzQsqDTzQY
 n7AcTSLWPkfTlBYhFZL1HCuWNi+YnIxX8qV24tV+ga+GaHOvVxCLtVkugk7NeVg=
 =tCvs
 -----END PGP SIGNATURE-----
 

Make get_host_triple public to get a triple from Bazel's repository_ctx (#1289)

I found half-baked duplicate implementations of this logic in
cargo-raze, in cxx, and in rules_rust's test suite of the
load_arbitrary_tool function. It seems such logic is necessary for
correctly using load_arbitrary_tool from the implementation of a
repository_rule.