-
Hi, is there an alternative to using cargo's per-package-target unstable feature? I have a workspace that has 2 packages, one which builds to However, more generally, I'm curious as to what the common workaround is for when a cargo workspace has a package that builds to a separate platform from the host? The |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @kuroahna! I know cargo allows configuring exactly which packages to build or exclude as part of the CLI arguments. For example I'd imagine you can do something like:
Generally speaking you should be able to set Hope this helps! |
Beta Was this translation helpful? Give feedback.
Hi @kuroahna! I know cargo allows configuring exactly which packages to build or exclude as part of the CLI arguments. For example I'd imagine you can do something like:
cargoExtraArgs = "--exclude your-wasm-package";
for the "native" derivationcargoExtraArgs = "--target wasm32-unknown-unknown -p your-wasm-package";
for the wasm derivationGenerally speaking you should be able to set
installPhaseCommand
(orinstallPhase
if you want to control running pre/post hooks yourself) to any arbitrary invocation you'd like. Check out the API docs for the specifics.Hope this helps!