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

asked 2019-07-31 10:57:06 +0300

martyone gravatar image

updated 2019-11-01 16:14:49 +0300

Update #1

Today (Nov 1) at 14:00 UTC we published an update to the Early Access Build Targets. These match the Sailfish OS release (Torronsuo) now.

If you have an older version of the Early Access Build Targets installed, you should see an update notification in the Sailfish SDK soon.

Please, read the following notes about the Early Access Build Targets:

  • The Early Access Build Targets match the latest Sailfish OS version released to Early Access users
  • By using the Early Access Build Targets developers can test their Sailfish OS apps a week before the Sailfish OS release is made public
  • During the early access time the Early Access Build Targets should not be used for submitting apps to the Jolla Harbour
  • Installation is done by selecting "Sailfish SDK > Sailfish OS Build Targets > SailfishOS-ea-<arch>" components inside the SDK Installer/Maintenance Tool

Happy hacking,

Jolla SDK Team

Sailfish SDK version 2.2

Today (July 31) at 07:00 UTC we published new installers and repositories of the Sailfish SDK. This SDK release is called 2.2 and among other changes it enables development for Sailfish OS release 3.1.0.

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

(*) Compared to, the latest release available on devices, contains additional SDK-specific updates.

Emulators and Build Targets for several older Sailfish OS releases remain available. Please see below for detailed information of the changes.

A couple of things you should be aware of:

  • Starting with this release, Git is a prerequisite for the Sailfish SDK on Windows - you can get Git from https://git-scm.com/download/win if it is not already installed on your workstation.
  • As before, in this update the Build Engine, Emulator and Targets are reinstalled so you will lose all changes you may have made in those. However, if your application packaging is done correctly, rebuilding your projects should reinstall the packages you have been using.
  • Any customization done to SDK (adding new package repositories, adding custom Targets, additional source paths) will be removed during the installation process so make your own backup of those before starting the update.
  • If you import existing projects made with a previous version of the SDK, make sure to select the correct kit in the project configuration step. Both ARM and i486 kits are available.
  • Package repository contents have been updated and consequently using a previous SDK version with these package repositories is not supported.
  • For more information, please see the Application SDK known issues list at https://sailfishos.org/wiki/Application_SDK_Known_Issues.

Release Content

Sailfish SDK 2.2

SDK IDE (Qt Creator)

  • Qt Creator updated to version 4.9
  • New Sailfish SDK User Manual and libsailfishapp documentation available in Help mode
  • Code model now respects possible additional arguments passed to qmake according to the .spec file
  • New APIs available:
    • Secrets and Crypto
    • Keepalive
  • Bugs fixed:
    • Application development SDK doesn't find include paths from PKGCONFIG
    • Changing SSH port and VM system properties of build engine in one step is broken
    • QtCreator crashes when adding new Sailfish OS emulator device
    • VM system properties cached at Qt Creator side out of sync after SDK upgrade
    • Failed to remove manually added translation files from project

SDK CLI (sfdk)

  • The new command line frontend to the Sailfish SDK
  • Enables convenient access to services available inside the Build Engine without the need to use the IDE
  • On Windows, it is recommended to use it from the Git Bash for the best experience
  • Find the "sfdk" executable inside the "bin" subdirectory of the SDK installation directory


  • Bugs fixed:
    • Some packages fail to install on emulator because the local repository cache is not initially populated
    • Applications cannot be uninstalled from launcher grid

Build Engine

  • Invalid (missing) package signatures are now ignored by default inside the SDK
  • Bugs fixed:
    • sdk-manage: Snapshots of targets provided by installer cannot be removed by user

Installer/Maintenance Tool

  • Components added for Build Targets matching the latest Sailfish OS version released to Early Access users

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 2019-07-31 10:57:25.642399



public repos please ) cant build my app, build on oldest target for now.

sashikknox ( 2019-07-31 20:28:30 +0300 )edit

Still no repos, this is getting annoying now :/

Allstar12345 ( 2019-08-10 12:50:45 +0300 )edit

hello guys, quick question, does make sense put more performance to build engine to faster reactions, or is it not needed? I have quite strong laptop, so there is lot of space for making it better :) I did not find any discussion regarding this. Also, I had VirtualBox openSUSE with SDK 2.1, everything worked. Two days back on this virtual came some update for the SDK to 2.2 aaand Build Engine and Emulator won't start up at all.. it worked before that.. It also seemd like VirtualBox itself got an update, so it might be also by that. It behave like when I had vt-x disabled on my laptop and Windows 10 was not able to run any VirtualBox VM, not sure what went wrong..

Bobsikus ( 2019-08-15 12:01:15 +0300 )edit

Is early access repo updated for ? At that moment, I still don't see any update available in SDK maintainance tool.

Damien Caliste ( 2019-11-04 12:39:04 +0300 )edit