error: failed to verify package tarball
Caused by:
Source directory was modified by build.rs during cargo publish. Build scripts should not modify anything outside of OUT_DIR.
Added: /me/rmin/target/package/rmin-examples-0.0.1/aaa.rmin.Rust.Functions.R
But since I only have a proc-macro and no build.rs, the OUT_DIR is not set. And since I need some of their output (generating R wrappers for further roxygen2 doc generation and further package loading), the output is necessary.
Is there some configuration that could make a OUT_DIR visible for proc-macros?
Proposed Solution
Currently, for build.rs, it could write output to OUT_DIR, but for proc-macro-only crate, such option does not exists.
Another solution is that adding a [cache] section in Cargo.toml, tell Cargo what file could be written. With this configure, we may have the ability to debug proc-macros by tell them writting down all the code they generates.
epage
commented
3 months ago
Problem
Currently, crates-io will yield such error:
But since I only have a
proc-macroand nobuild.rs, theOUT_DIRis not set. And since I need some of their output (generating R wrappers for further roxygen2 doc generation and further package loading), the output is necessary.Is there some configuration that could make a
OUT_DIRvisible forproc-macros?Proposed Solution
Currently, for build.rs, it could write output to
OUT_DIR, but forproc-macro-only crate, such option does not exists.Another solution is that adding a [cache] section in Cargo.toml, tell Cargo what file could be written. With this configure, we may have the ability to debug proc-macros by tell them writting down all the code they generates.
Notes
No response