Loading…

Bringing Swift to Arm SBC's

Downloads, Code Examples and More...
Start exploring

Swift 4.1.2 Updated For RaspberryPi 2/3

Update: There is a new “Release” repository with newer versions of Swift 4.2.* available.

Swift 4.1.2 updates are now available for Ubuntu 16.04 and Raspbian Stretch on the RaspberryPi3 and RaspberryPi2.

Please Note: Uninstall Swift before trying to install a new version.

    1. Add repo
      curl -s https://packagecloud.io/install/repositories/swift-arm/debian/script.deb.sh | sudo bash
    2. Install Swift for Ubuntu 16.04
      sudo apt-get install swift-4.1-RPi23-Ubuntu1604
    3. Install Swift for Raspbian Stretch
      sudo apt-get install swift-4.1-RPi23-RaspbianStretch

11 thoughts on “Swift 4.1.2 Updated For RaspberryPi 2/3

  1. Hello there,

    Could you publish a snap package for Ubuntu Core? I have tried a few Swift snappy there, but It haven’t worked at all.

    I wonder if the prebuilt binary of Swift for Ubuntu Mate can work for Ubuntu core? Do you have any idea? Thanks in advance.

    I’m not embedded programming guy, so for my dumb questions.

      1. Thanks admin for fast replying.

        I spent the whole night to setup up Snappy Ubuntu Core for Swift, and I gave up. But thanks for your suggestion about the “Classic” mode in there, I will try in another day.

        I have switched over to Raspbian OS. It make me feel amazing. Because the boot time of raspbian OS is very fast over Snappy Ubuntu Core. I have setup all things including Swift in a hour.

        I believe Raspbian is a right choice now.

  2. Thanks for your work here. I installed this yesterday on Raspbian and was able to get basics working, but ran into trouble with SwiftPM when trying to build Vapor and Kitura. Is this something you would expect to work on Raspbian, or should I switch to Ubuntu?

    1. Hi Barry,
      Which version of Swift do you have installed? and can you post some of the errors you are getting.
      Thanks.

      1. I was able to track my SwiftPM problems down to having exported GIT_DIR and GIT_WORKING_DIR. Unsetting those resolved it.

Leave a Reply