We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, the idiom to use shadow-rs is depending on it for both build-dependencies and dependencies.
shadow-rs
build-dependencies
dependencies
However, the code necessary in build time is not always used in runtime, such as git2, tzdb, extra.
git2
tzdb
I suppose we can provide a runtime-only crate for users.
I currently try inline the shadow! macro:
shadow!
pub mod build { include!(concat!(env!("OUT_DIR"), "/shadow.rs")); }
and get the compile error:
| 252 | pub const VERSION:&str = shadow_rs::formatcp!(r#" | ^^^^^^^^^ use of unresolved module or unlinked crate `shadow_rs`
So perhaps we can provide a shadow-lib crate that contains only the macro and reexport formatcp!?
shadow-lib
formatcp!
cc @baoyachi
The text was updated successfully, but these errors were encountered:
Work it around now with:
pub mod build { mod shadow_rs { pub use const_format::formatcp; } include!(concat!(env!("OUT_DIR"), "/shadow.rs")); }
Sorry, something went wrong.
No branches or pull requests
Currently, the idiom to use
shadow-rs
is depending on it for bothbuild-dependencies
anddependencies
.However, the code necessary in build time is not always used in runtime, such as
git2
,tzdb
, extra.I suppose we can provide a runtime-only crate for users.
I currently try inline the
shadow!
macro:and get the compile error:
So perhaps we can provide a
shadow-lib
crate that contains only the macro and reexportformatcp!
?cc @baoyachi
The text was updated successfully, but these errors were encountered: