Arch Linux User Repository

hm. Different compiler versions could be an issue. But different workspaces with different build settings shouldn't be. The official documentation doesn't say anything against a shared target directory, as far as I've seen, and Stackoverflow also says that it should work (although Shepmaster questions its benefits).

That said, after doing some more research it seems that no AUR package currently supports my attempt to share build outputs. The build either breaks if CARGO_TARGET_DIR is set or it's ignored, because --target-dir is passed to cargo.

So, never mind :)

A global cargo target dir is a terrible idea. Sharing it between multiple workspaces and compiler versions (both of which will inevitably happen) will cause needless issues unless you nuke it between runs — in which case the "sharing" is pointless.

Instead of setting --target-dir, I think it is better to set CARGO_TARGET_DIR via export CARGO_TARGET_DIR=${CARGO_TARGET_DIR:-target} in build and use ${CARGO_TARGET_DIR:-target} instead of target in package.

The environment variable overrules the target-dir setting and still allows people to set CARGO_TARGET_DIR globally in order to put all built crates into one place.

Thanks for your response. It works well now.

@gyara: Sorry for the delay, a new version has just landed containing your suggestion. In a clean environment (Docker container) it still builds fine, please test whether your build-issue is fixed too.

this PKGBUILD file can not work when I set target dir in cargo config. May use --target-dir $PWD/target option to fix?