You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building a C library from rust code we have to pass rust_crate_type: 'cdylib' or rust_crate_type: 'staticlib' depending if it's a shared_library() or static_library(). But in the case of both_libraries() or library() the value must be different depending on default_library option.
We probably need to add a new value rust_crate_type: 'clib' to mean cdylib if shared library, staticlib if static library.
The text was updated successfully, but these errors were encountered:
Note that we already handle this correctly if rust_crate_type is omitted, but it default to building Rust library rlib or dylib. This raises the question: Do we even need all possible values for rust_crate_type? rlib vs dylib and cdylib vs staticlib is something meson already knows. The only thing user needs to specify is if it's a rust or c lib.
When building a C library from rust code we have to pass
rust_crate_type: 'cdylib'
orrust_crate_type: 'staticlib'
depending if it's a shared_library() or static_library(). But in the case of both_libraries() or library() the value must be different depending on default_library option.We probably need to add a new value
rust_crate_type: 'clib'
to meancdylib
if shared library,staticlib
if static library.The text was updated successfully, but these errors were encountered: