tree b4f5bd7b0e933a025bdd8c4f114bb6bdc0d018d5
parent 0175a1b7aaada0ea34c984c30c245da2a56e8d6c
author scentini <rosica@google.com> 1651156320 +0200
committer GitHub <noreply@github.com> 1651156320 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiaqVgCRBK7hj4Ov3rIwAATEwIAEDcG5AT+fhvm+3lzdK1mpry
 mQBqVPoF+RT90jDtdhQ+HAJYHRt23MIn/yobjhGc2rsiPI7MWLJe0zFg2X4EQOEw
 zFigFiOgoslUJ9ILw5rn6CrQBr3kK6Lsf6pIVU6WPaGli09SRlSoAnYhOiQ1ZGfw
 Iafw0o1M5ivyXQ9Z7vuCBSDrKtvnmtzTpsmed+6M/YaageOazkmuy6KlIspJh5Em
 XXAe5XngboAVw+2bKfCVzhoJTCUiW/Gnk9w36rdaCIbInCdC+tA3PaCxM6kVTEKK
 Ihao/Re91VZR569eCOkh1z/tTjrxJQ9p4byhJOKPT9b5ekTQt061RXqbCbZFPpg=
 =ZJbQ
 -----END PGP SIGNATURE-----
 

Don't emit `CrateInfo` from `rust_static_library` and `rust_shared_library` (#1298)

These rules emit a `staticlib` and `cdylib` which are not meant for consumption by other rust targets.

However, one should still be able to write a `rust_test` for `rust_shared_library` and `rust_static_library` targets, which needs a `CrateInfo`. For this purpose we provide a `CrateInfo` wrapped in a `TestCrateInfo` provider, that `rust_test` understands.