[release notes] Sailfish SDK 3.1 [not a question]

asked 2020-04-30 13:21:30 +0300

martyone gravatar image

updated 2020-05-07 14:11:40 +0300

Sailfish SDK 3.1

Update #1 - 7.5.2020


Today (May 7th) at 11:00 UTC the Sailfish SDK 3.1 has been released to all users. Please, check out the in depth release notes from below.

The installers for this release of the SDK are now available at http://sailfishos.org/wiki/Application_SDK#Latest_SDK_Release. If you have an older release of the SDK, you should see an update notification in the Sailfish IDE.

If you have any questions, feel free to either send an email to this mailing list: devel at lists.sailfishos.org, write it up in http://together.jolla.com and tag your issue with 'sdk' or send an e-mail to developer-care at jolla.com.

Happy hacking,

Jolla SDK Team

Release notes - 30.04.2020

Today (April 30, 2020) at 10:00 UTC we published new installers new installers and repositories of the Sailfish SDK to Early Access users. This SDK release is called 3.1.

Most notable changes included in this release:

  • GCC 8.3.0
    • The Sailfish OS 3.3.0 build targets use GCC 8.3.0, which brings support for C++17 and many other improvements
  • Clang Code Model
    • The SDK IDE (Qt Creator) now uses Clang Code Model for coding assistance
  • Docker-based build engine (Linux and Windows)
  • Remote debugging with sfdk, the CLI frontend to Sailfish SDK
  • Online installation is the default option now
    • Offline installers allow installation with VirtualBox-based build engine, latest build targets and latest emulator on hosts with limited network access
  • End of 32-bit Linux support

Contributions from Aurora SDK:

Several of the key improvements in this release were developed in collaboration with Open Mobile Platform for Aurora SDK. Here are some of the key features contributed by Open Mobile Platform to the Sailfish SDK:

  • GCC 8.3.0
  • SDK IDE: Clang Code Model, performance improved
  • SFDK: remote debugging, deployment improvements, undeploying packages, bugs fixed
  • Qt Linguist: bugs fixed
  • Emulator: bugs fixed
  • Build Engine: Docker support (Linux and Windows), improved compilation speed, improved reporting, bugs fixed

We would like to thank the people who have reported bugs via together.jolla.com.

Release Content

The latest Emulator and Build Targets match the Sailfish OS release (Rokua)

Sailfish SDK 3.1

SDK IDE (Qt Creator)

  • Clang code model
  • Bugs fixed:
    • SDK on Windows: build/run taking a lot longer than it used to
    • Qt Creator on newer Windows: No winrtrunner.exe found
    • Updating to the latest SDK (3.0.7) the numeric pad and much others keys don't work anymore in Qt Creator
    • SDK 3.0: Issue with rsync when deploying to device
    • When changing the device Name in Emulator Modes, the cursor moves to the end of the line
    • Sailfish IDE crashes when adding new kit
    • Inaccessible virtual machines inside available virtual machines list

SDK CLI (sfdk)

  • Deployment improvements
  • Undeploying packages
  • Remote debugging
  • Bugs fixed
    • sfdk config search-output-dir option allows setting arbitrary values
    • Inaccessible virtual machines inside available virtual machines list
    • sfdk fails to apply patches when %autosetup -pN is used

Qt Linguist

  • Bug fixed:
    • Qt Linguist crashes on file save


  • Bugs fixed:
    • Ignored sshd configuration file under SDK VMs

Build Engine:

  • Docker-based build engine (Linux and Windows)
  • VirtualBox-based build engine settings have been optimized to improve compilation speed
  • sdk-assistant has improved error reporting
  • Bugs fixed:
    • Packages built with SDK do not correctly record BUILDHOST in their metadata
    • Invalid cpio option used while building an RPM in the SDK build engine
    • Automatically created build engine snapshot is confusing and suggests dangerous use

Build Targets:

  • GCC 8.3.0
  • Bugs fixed:
    • Apps repository is disabled by default on SDK targets
    • SDK 2.2.3: Could not resolve the prototype "SilicaItem" of "PageHeader"


  • Online installers
  • With Docker-based build engine chosen, VirtualBox becames an optional dependency required by Sailfish OS emulators only
  • 32-bit Linux installers and repositories are not distributed anymore
  • Bugs fixed:
    • Updating SDK components failed
    • Uninstalling Sailfish SDK shows errors
    • Error message dialogs during SDK installation

If you have any questions, feel free to either send an email to SailfishDevel mailing list: devel at lists.sailfishos.org, write it up here in http://together.jolla.com and tag your issue with 'sdk' or send an e-mail to developer-care at jolla.com.

Happy hacking!

Jolla SDK Team

edit retag flag offensive reopen delete

The question has been closed for the following reason "not a real question" by martyone
close date 2020-04-30 13:21:45.197727



It might be worth adding that Docker for Windows requires either 10 pro or enterprise editions.

Allstar12345 ( 2020-04-30 15:40:33 +0300 )edit

Why has this been clsoed?, I have no end of problems with this new release. Wow, where to start moaning!, I'm so angry and disappointed with this new SDK, I knew I should have stayed on the earlier version 3.0.7, which I not from the downloads page has been removed. It's going to take me hours to communicate the amount of problems I have, grrrrr. As usual, more time is spent trying to set up the SDK than it is using it!

I note there are bugs fixed?, bugs that were not present in 3.0.7 and are now blatant in 3.1.7 yet claim to be fixed, unreal, thanks guys. Either I'm stupid (probably) or there are just way too many problems with the new SDK.

Spam Hunter ( 2020-05-08 13:46:43 +0300 )edit

Edz: actually this update of SDK went lot smoother to me than before I have another "issue", it is not exactly issue, but it slows me a bit. is it possible to disable necessity to approve installation of package in the emulator ?! For the first time I have wondered, why it takes ages to compile and was doing something else and let it running in the background... now I have to do it manually every time.. It is not something I could not do, but something I would love not do every time :)

Bobsikus ( 2020-06-05 16:22:44 +0300 )edit