[release notes] Sailfish SDK 3.4

Update History

  • 2021-02-19 Sailfish SDK 3.4 released to Early Access users
  • 2021-02-26 Sailfish SDK 3.4 released to all users
  • 2021-05-12 Early Access Build Targets updated to 4.1.0.23 (Kvarken)

Contributions from Aurora SDK and the developer community

The key improvements in this release were developed in collaboration with Open Mobile Platform for Aurora SDK.

We would also like to thank the people who have reported bugs via Sailfish OS Forum.

Most notable changes included in this release

  • General: The SDK installer has been updated so that itā€™s possible to install the SDK on recent Linux distributions without installing packages from older distributions, added option to run rpmlint on mb2/sfdk, PackageKit improved, bug fixes

  • SDK IDE (Qt Creator): user notification improved, bug fixes

  • SDK CLI (sfdk): sfdk tools improved, added undeploy packages without root;
    added possibility to use task name to create a subdirectory, added --no-check option, bug fixes

  • Emulator: emulator now includes the standard settings application, bug fixes

  • Build Engine: build engine and connection improved, bug fixes

  • In previous versions of the SDK, the project sources were expected to be under the user home directory, or a separate ā€œalternative source folderā€. This has been unified now so that the sources are always expected to be under a ā€œworkspaceā€ - which can be the user home directory.

Release Content

The latest Emulator and Build Targets match the Sailfish OS release 4.0.1 ā€œKoliā€

SDK IDE (Qt Creator)

  • When configured to use Early Access SDK releases, SDK IDE checks for updates daily
  • User is notified when any of the ports configured for SSH access to SDK virtual machines is used by another application
  • Bugs fixed:
    • Typos in settings dialog
    • No suitable kits found

SDK CLI (sfdk)

  • New built-in test suite for running rpmlint (enabled by default)
  • Possibility to undeploy packages from devices without root access via ā€˜sfdk undeploy --sdkā€™
  • The ā€˜taskā€™ configuration option is now used to create a subdirectory instead of prefixing output directory name
  • Interactive sfdk sessions no longer perform reverse path mapping on output. From now on you see the paths as they exist inside the build engine.
  • The build and package commands now have --no-check option
  • Bugs fixed:
    • Installing tooling with sfdk hangs on Windows
    • sfdk on Windows: false positive detection of Git changes due to CRLF line terminators
    • sfdk tools list requires network connection
    • sfdkā€™s no-pull-build-requires option is broken
    • sfdk executed by installer complains about not running under MSYS shell
    • sfdk: The ā€˜buildā€™ command silently picks ā€œsomeā€ default build target
    • False detection of untagged changes with projects created by sfdk-init
    • sfdk: QObject::startTimer: Timers can only be used with threads started with QThread

Emulator

  • Standard settings application
  • Modes for Xperia XA2 and 10 models
  • Bugs fixed:
    • Sound is really low from a running project
    • Emulator does not start with default settings under Hyper-V
    • DBUS_SESSION_BUS_ADDRESS is not set when running commands over ssh on emulator
    • SDK Emulator Wayland pattern is not compatible with meta-packages layout
    • Error connecting to emulator virtual machine when running project on Windows10
    • Sailfish emulator displayed USB dialog on first boot
    • ā€œDate and timeā€ and ā€œData countersā€ pages in Settings cannot be opened

Build Engine

  • SDK Control Centre, which was deprecated in Sailfish SDK 3.0, has been removed
  • createrepo_c upgraded to 0.12.0
  • GNU Bash upgraded to 5.0.18
  • Bugs fixed:
    • Docker based build engine: Repositories under build targets not refreshed initially
    • ā€œposix_spawn avoidedā€ message pollutes build output
    • Build target update is silently skipped after tooling update non-fatal error
    • Connection timeout right after build engine start - random number generator not ready
    • Connection to build engine fails if ssh-agent has more than 5 keys
    • False detection of untagged changes due to the dynamic executable permission handling
    • sdk-manage complains about hostname
    • rpmlint not preinstalled under SDK toolings while it should be
    • mb2 --help displays obsolete usage text
    • No files visible in project tree for CMake based projects
    • High CPU load caused by build engine in idle state

General

  • SDK is installable on recent Linux distributions (e.g. Ubuntu 20.04)
  • OpenSSL ARM capability detection is disabled while debugging. This can be toggled via checkbox in project run settings.
  • Improved error reporting during package deployment
  • Add option to run rpmlint on mb2/sfdk build
  • Dependencies for python apps should be generated automatically. If this is an issue for you, you have two options:
    • Disabling depencency to a single module by adding a line in your .spec file, where module is the name of the problematic module: %define __requires_exclude python3dist.module
    • Disabling automatic python app depencency generation completely by adding a line in your .spec file: %undefine __pythonapp_requires
  • Made SDK installable on recent Linux distributions
  • Added Notification Gallery as an example app
  • Bugs fixed:
    • Noninteractive install on Windows hangs on Start Menu shortcuts page
    • Uninstalling SDK when target snapshots exist fail
    • Installing SDK on a fresh Windows 10 machine fails with 0xc000007b
    • PackageKit does not allow to prevent removal of a required package

If you have any questions, feel free to either write it up here in Sailfish OS Forum or send an e-mail to developer-care at jolla.com.

Happy hacking!

Jolla SDK Team

Today (February 19, 2021) at 11:00 UTC the Sailfish SDK 3.4 release was published to Early Acces users. Please, check out the in depth release notes from original post.

The installers for this release of the SDK are now available at https://sailfishos.org/wiki/Application_SDK_Early_Access#Latest_Early_Access_SDK_Release

If you have an older release of the SDK with the early access updates repository enabled, 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

Today (February 26th, 2021) at 11:00 UTC the Sailfish SDK 3.4 release was published to all users. Please, check out the in depth release notes from original post.

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

1 Like

Today (May 12th) at 13:00 UTC we published an update to the Early Access Build Targets. These now match the Sailfish OS release 4.1.0.23 (Kvarken).

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