[release notes] Sailfish SDK 3.2

Announcements
#1

Update #3 - 30.9.2020

Today (Sep 30th) at 08:00 UTC we published an update to the Early Access Build Targets. These now match the Sailfish OS release 3.4.0.22 (Pallas-Yllästunturi).

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 about 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

If you have any questions, feel free to either write it up here in https://forum.sailfishos.org/ or send an e-mail to developer-care at jolla.com.

Happy hacking,

Jolla SDK Team

Update #2 - 15.09.2020

Today (September 15th) at 08:00 UTC we published a bug-fix update to the Sailfish SDK 3.2 release.

This update addresses occasional errors with file sharing between the host and the build engine, possibly causing silent corruption of software packages produced with this SDK release. All users are advised to update.

Users who have Sailfish SDK installed should see an update notification in the Sailfish IDE. Updated installers are now available at http://sailfishos.org/wiki/Application_SDK#Latest_SDK_Release .

If you have any questions, feel free to either write it up here in https://forum.sailfishos.org/ or send an e-mail to developer-care at jolla.com.

Happy hacking,

Jolla SDK Team

Update #1 - 11.08.2020

Today (August 11th) at 12:00 UTC the Sailfish SDK 3.2 release was published 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 write it up here in https://forum.sailfishos.org/ or send an e-mail to developer-care at jolla.com.

Happy hacking,

Jolla SDK Team

Release notes - 30.07.2020

Today (July 30, 2020) at 08:00 UTC we published new Sailfish SDK installers and repositories to Early Access users. This SDK release is called 3.2.

Most notable changes included in this release:

  • Added support for CMake-based projects.

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 improvements contributed by Open Mobile Platform to the Sailfish SDK:

  • Support for CMake
  • Support for projects with multiple .spec files
  • Use of user-supplied SSH keys for device access
  • Build engine, Qt creator, SDK CLI: 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 3.3.0 “Rokua”

SDK IDE (Qt Creator):

  • Support for CMake added.
    • It is possible to create a CMake-based Sailfish OS application project either
      1. from Qt Creator, by using the Sailfish OS Qt Quick Application wizard as usually, but selecting CMake on the new Build System page, or
      2. with sfdk init command by passing the -b|--builder option with cmake as argument.
    • None of the currently available build targets come with CMake preinstalled – be sure to declare BuildRequires: cmake in your .spec file.
  • Support for projects with multiple .spec files
    • Particular .spec file can be selected in project’s build settings, under the Sailfish SDK Settings category. It is also possible to specify additional sfdk configuration options there.
  • Use of user-supplied SSH keys for device access
    • This also fixes the issue that SSH keys for HW devices are not preserved during SSH upgrade
    • You will still need to re-register your HW devices after upgrading this time
  • Bugs fixed:
    • Prevent extra password queries when connecting SDK to a physical device
    • Qt Creator: Our plugin used to be called just “OS” instead of “Sailfish OS”

SDK CLI (sfdk):

  • CMake-based projects can also be handled with sfdk commands
  • Enabled shadow builds for Autotools-based projects
  • Added build-shell command for running custom build steps and tools exec command for running custom maintenance commands under build tools
  • Added compiledb command for generating compile_commands.json file (see https://doc.qt.io/qtcreator/creator-clang-codemodel.html#using-compilation-databases for possible use)
  • Bugs fixed
    • sfdk: failed to deploy app on emulator with zypper

Emulator:

  • Bugs fixed:
    • Application used to exit with error code 1 due to time-consuming VM boot process

Build Engine:

  • Advice in out-of-memory situations
  • Possibility to setup swap for the Build Engine
  • Bugs fixed:
    • Closing the Manage Build Target wizard is now prevented while the Search packages command is in progress to avoid RPM database corruption
    • The incorrect static definition of Host: localhost in the build engine options dialog in Qt Creator replaced with the actual host name/address which is used for connecting to the build engine
    • Scripts in a project directory are not always runnable in the build engine
    • Proxy settings is ineffective with Docker-based build engine
    • mb2: the same qmake variables cache is used for all build targets

If you have any questions, feel free to either write it up here in https://forum.sailfishos.org/ or send an e-mail to developer-care at jolla.com.

Happy hacking!

Jolla SDK Team

17 Likes
[SDK] version numbering
After upgrade to 3.4.0.24 caldav sync stopped working