Including parent directory in Docker context when dealing with complex projects?

[ipsi]

I'm trying to build the Anki Sync Server on a macOS host for an ArmV7 Linux target (so I can run it on my NAS). That's part of a workspace, which is fine, but it also depends on things outside of the Rust workspace (e.g., the ftl directory). Is there any way that I can include the parent folder of the rslib dir when building? I didn't see anything the docs that looked helpful.

EDIT: the specific error I'm seeing is

error: failed to run custom build command for `anki_i18n v0.0.0 (/Users/ipsi/workspace/anki/rslib/i18n)`

Caused by:
  process didn't exit successfully: `/target/release/build/anki_i18n-17b05a731123a3d9/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=../../ftl/core/actions.ftl
  cargo:rerun-if-changed=../../ftl/core/adding.ftl
  cargo:rerun-if-changed=../../ftl/core/browsing.ftl
  cargo:rerun-if-changed=../../ftl/core/card-stats.ftl
  cargo:rerun-if-changed=../../ftl/core/card-template-rendering.ftl
  cargo:rerun-if-changed=../../ftl/core/card-templates.ftl
  cargo:rerun-if-changed=../../ftl/core/change-notetype.ftl
  cargo:rerun-if-changed=../../ftl/core/custom-study.ftl
  cargo:rerun-if-changed=../../ftl/core/database-check.ftl
  cargo:rerun-if-changed=../../ftl/core/deck-config.ftl
  cargo:rerun-if-changed=../../ftl/core/decks.ftl
  cargo:rerun-if-changed=../../ftl/core/editing.ftl
  cargo:rerun-if-changed=../../ftl/core/empty-cards.ftl
  cargo:rerun-if-changed=../../ftl/core/errors.ftl
  cargo:rerun-if-changed=../../ftl/core/exporting.ftl
  cargo:rerun-if-changed=../../ftl/core/fields.ftl
  cargo:rerun-if-changed=../../ftl/core/findreplace.ftl
  cargo:rerun-if-changed=../../ftl/core/help.ftl
  cargo:rerun-if-changed=../../ftl/core/importing.ftl
  cargo:rerun-if-changed=../../ftl/core/keyboard.ftl
  cargo:rerun-if-changed=../../ftl/core/media-check.ftl
  cargo:rerun-if-changed=../../ftl/core/media.ftl
  cargo:rerun-if-changed=../../ftl/core/network.ftl
  cargo:rerun-if-changed=../../ftl/core/notetypes.ftl
  cargo:rerun-if-changed=../../ftl/core/preferences.ftl
  cargo:rerun-if-changed=../../ftl/core/profiles.ftl
  cargo:rerun-if-changed=../../ftl/core/scheduling.ftl
  cargo:rerun-if-changed=../../ftl/core/search.ftl
  cargo:rerun-if-changed=../../ftl/core/statistics.ftl
  cargo:rerun-if-changed=../../ftl/core/studying.ftl
  cargo:rerun-if-changed=../../ftl/core/sync.ftl
  cargo:rerun-if-changed=../../ftl/core/undo.ftl

  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', rslib/i18n/gather.rs:63:37
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[Emilgardis]

Absolutely, see *.env in the readme

basically

[build.env]
volumes = [
    "FTL_DIR=/path/to/ftl",
]

it'll be mounted in the container at the same path as on the host.

[ipsi]

Thanks! It wasn't immediately clear to me where those volumes would wind up, or if they were using the docker syntax for mounting.

I think my actual problem was unrelated in the end:

1. I'm a muppet and there's a Cargo.toml file in the top-level directory
2. The build process is more complex than I initially realised, and there are a number of scripts that need to be run first

Between the two of them it now builds successfully with Cross.