Question 1

How do I set up Swish with Xcode for remote Swift builds?

Accepted Answer

Install Swish via Homebrew, then in Xcode, add an External Build System target, set the build tool to /bin/bash with arguments like 'swish '. Ensure SSH keys are configured on the remote Linux machine as per the README steps.

Question 2

Swish vs Docker for Swift development on Linux?

Accepted Answer

Swish integrates remote Linux builds into Xcode via SSH, ideal for direct compilation from macOS. Docker offers containerized local environments for consistency but doesn't tie directly into Xcode's build system. Swish is better for Xcode-centric workflows with remote machines.

Question 3

Can Swish be used with Swift Package Manager?

Accepted Answer

The README doesn't specify, but since Swish builds Swift projects remotely, it should work with SPM if the remote machine has it installed. You may need to ensure the project structure and dependencies are set up correctly on the Linux side.

Question 4

Does Swish support debugging on remote Linux machines?

Accepted Answer

No, Swish focuses on compilation; debugging requires separate tools. The README suggests running the project via SSH after building, so you'd need to use command-line debuggers like LLDB on the remote machine manually.

Question 5

What if my SSH connection fails during a build?

Accepted Answer

Swish relies on SSH, so check key authentication, network connectivity, and remote machine accessibility. The README provides setup steps for SSH keys, but troubleshooting network issues is up to the user.

Question 6

Is Swish compatible with ARM-based Linux like Raspberry Pi?

Accepted Answer

Yes, the README includes an installation script for Swift on Raspberry Pi 3, indicating support for ARM devices as remote build targets.

Swish

What is Swish?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions