```chrisjrn@chrisjrns-MacBook-Pro pants % ./pants ...
# development
a
Copy code
chrisjrn@chrisjrns-MacBook-Pro pants % ./pants --keep-sandboxes=on_failure export-codegen src/rust/engine:compile_rust
09:42:54.04 [INFO] Preserving local process execution dir /private/var/folders/0m/h2n902qn38b8555xq8z0w_h40000gn/T/pants-sandbox-EdlSZp for Testing candidate for `python3` at `/Users/chrisjrn/.pyenv/shims/python3`
09:42:54.04 [INFO] Completed: Testing candidate for `python3` at `/Users/chrisjrn/.pyenv/shims/python3`
09:42:54.05 [INFO] Writing generated files to dist/codegen
chrisjrn@chrisjrns-MacBook-Pro pants % ls ./dist/codegen/src/rust/engine/target/debug
build           examples        libclient.d     libengine.d     pants
deps            incremental     libclient.rlib  libengine.dylib pants.d
chrisjrn@chrisjrns-MacBook-Pro pants %
πŸ‘€
πŸ’― 2
πŸŽ‰ 2
It still reads a cargo cache from outside the Pants sandbox, and it’s probably not incremental enough for development work just yet, but it does seem to work.
f
via shell backend or a new rust backend?
a
by
adhoc_tool
, for now.
The goal at the moment is to make the native engine code more amenable to frequent branch switching