Help trying to compile macrdp via Cargo build

help
1

So I've been trying to install macrdp, which seems to be built in Rust, on an Intel iMac.

The project was last updated 6 months ago, so it can't be that out-of-date.

And the iMac I'm trying to use, while older, is running Sequoia, which isn't that old either...

I had a hell of a time figuring out how to get `cargo build --release` to run at all. It's working now, mostly, after changing DYLD_LIBRARY_PATH in config.toml to DYLD_LIBRARY_FALLBACK_PATH, but still seems to be failing at this build step:

error: failed to run custom build command for `screencapturekit v1.5.4`

 Caused by:
  process didn't exit successfully: `/Users/admin/Downloads/macrdp-main/target/debug/build/screencapturekit-52e401cb88bd4798/build-script-build` (exit status: 101)
  --- stdout
  cargo:rustc-link-lib=framework=ScreenCaptureKit
  cargo:rerun-if-changed=swift-bridge

  --- stderr
  Swift build STDOUT:

  Swift build STDERR:
  error: Unknown option '--scratch-path'
  Usage: swift build <options>
   See 'build -help' for more information.


  thread 'main' (45022) panicked at /Users/admin/.cargo/registry/src/.index.crates.io-1949cf8c6b5b557f/screencapturekit-1.5.4/build.rs:119:9:
  Swift build failed with exit code: Some(64)
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

warning: build failed, waiting for other jobs to finish...

Is there any Rust expert out there that might be able to clue me in on how to fix this build process? I feel so close now.

2

The build script for the library screencapturekit is trying to invoke the swift command (to compile Swift code), and the --scratch-path option is not recognized by swift.

Perhaps this is because your Swift toolchain is older, or perhaps this is a bug in some way. (I am not familiar with building Swift code.) If the problem is that your Swift toolchain is older, then you will need to install a newer one, or ask the maintainers of screencapturekit if they can modify their build script to work with older Swift toolchains.

3

Thanks. I cross-posted this on Reddit and it did indeed end up being a problem with the Swift version. I already had newer versions installed, but in previous troubleshooting steps I think I had changed the global default to an older version. In case anyone runs across this post with a similar issue, running swiftly use --global-default 6.3.3 to change the "active" or "in use" Swift version fixed my issue.

But now I've run into a new problem. :frowning: