Cannot use rust_shared_library as a dependency of rust_library_group

[ashi009]

ERROR: <redacted>/proj2/wasm/BUILD.bazel:8:19: in deps attribute of rust_library_group rule //proj2/wasm:_normal_deps: '//proj1/wasm:wasm' does not have mandatory providers: 'CrateGroupInfo' or 'CrateInfo'

However, it's ok to put this target under the deps of another rust_shared_library

[UebelAndre]

I think this is by design. rust_library_group is supposed to represent a collection of rusr_library targets (e.g. targets that produce rlib files) where rust_shared_library produces dynamic lib files and tends to be an output from rust into other languages. That’s why the rule doesn’t return these providers.

[ashi009]

Does that mean we need to create another rust_library for the rust_shared_library to depend on first? So that the other rust_shard_library could depend on it? Sent from Gmail Mobile UebelAndre ***@***.***>于2025年1月25日 周六下午12:33写道：

…

I think this is by design. rust_library_group is supposed to represent a collection of rusr_library targets (e.g. targets that produce rlib files) where rust_shared_library produces dynamic lib files and tends to be an output from rust into other languages. That’s why the rule doesn’t return these providers. — Reply to this email directly, view it on GitHub <#3204 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFH2B3BKD7QHBHLXZXTSIT2MMHZHAVCNFSM6AAAAABV24YGJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTG43TINRYGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[UebelAndre]

Yeah, I would recommend that if you wanted to share the code.

[UebelAndre]

Gonna close this out for now since the behavior is currently expected.