[Release notes] Sailfish SDK 3.9

Update History

  • 2022-03-31 Sailfish SDK 3.9 released to Early Access users
  • 2022-04-08 Sailfish SDK 3.9 released to all users
  • 2023-02-02 Early Access Build Targets and Emulator updated to 4.5.0.16 (Struven Ketju)

Most notable changes included in this release:

  • The latest Emulator and Build Targets match the Sailfish OS release 4.4.0 “Vanha Rauma”
  • Fixed coding assistance for Sailfish.Silica types (code completion and static code checking)
  • Possibility to use Docker-based SDK on a (headless) multi-user host
  • sfdk’s built-in manual has been expanded

Contributions from the community

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

Release Content

The latest Emulator and Build Targets match the Sailfish OS release 4.4.0 “Vanha Rauma”

SDK IDE (Qt Creator)

  • Possibility to enable running qmake’s system() during project parsing - see Known Issues
  • The default Help viewer backend has been changed to LiteHtml on Linux and macOS. The QtWebEngine backend is known to fail on some newer Linux distributions at least.
  • Bugs fixed:
    • No feedback when attaching debugger to running application takes too long
    • Various warnings are produced by the QML static code checker for Sailfish.Silica types with the build targets matching recent Sailfish OS release
    • Kits for custom targets installed with --no-snapshot are badly named

SDK CLI (sfdk)

  • Expanded introductory sections in the built-in manual (sfdk --help-all)
  • Use ‘sfdk build-requires diff/reset’ without RPM SPEC
  • Bugs fixed:
    • sfdk can delete packages just built if EVR is computed
    • sfdk complains no journal files were found
    • sfdk: The --no-snapshot option is not actually recognized by ‘tools install-custom’
    • sfdk: failure to reset build target snapshots after bluez 4 to 5 update
    • sfdk build-shell --maintain discards command’s exit code
    • sfdk does not fix Version tag appearing in an included RPM .spec file
    • sfdk: Invalid cross-device link error when resetting build target snapshot – see Unable to build CMake project from QtCreator
    • Some binaries located under build directory cannot be executed under the build environment
    • sfdk: the ‘package’ command does not honor the ‘task’ configuration option
    • sfdk is verbose about unsigned cached packages

General

  • Allow MPRIS API in Harbour
  • Deprecate QtWebKit API in Harbour
  • App template includes X-Sailjail section
  • Bugs fixed:
    • Sailfish WebView API does not work on emulator
    • Scratchbox2 adds sb2 scripts and wrappers to path without checking if they are mapped into the target
    • mb2 fails to install build dependencies under Platform SDK installed under custom prefix
    • RPM validator treats comments in X-Sailjail as keys

Installation/Maintenance

Known Issues

  • The Amber.Mpris QML module is not initially recognized by the IDE
    • This can be fixed by installing the ‘amber-qml-plugin-mpris’ package under build targets using Options > Sailfish OS > Build Engine > Manage Build Targets… > Manage Packages
  • Sailfish IDE may not find header files from packages added as dependencies via PKGCONFIG qmake variable.
    • This is often caused by “qmake system() behavior when parsing” option under Build Settings set to “Ignore”. See the next item to learn about the drawbacks before changing it to “Run”.
  • Qmake’s system() function is ignored by the project parser under the default configuration.
    • This is controlled by the “qmake system() behavior when parsing” option under Build Settings.
    • It is ignored by default because it runs directly on host, not under the build environment as one would expect.

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

6 Likes

Today (March 31th, 2022) at 12:30 UTC the Sailfish SDK 3.9 release was published to Early Access users. Please, check out the in depth release notes from original post.

The installers for this release of the SDK are now available for download

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 (April 8th, 2022) at 07:30 UTC the Sailfish SDK 3.9 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 for download

If you have an older release of the SDK, you should see an update notification in the Sailfish IDE soon.

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

2 Likes

Today (Feb 2nd) at 13:00 UTC we published an update to the Early Access Build Targets and Emulator. These now match the Sailfish OS release 4.5.0.16 (Struven Ketju).

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

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

  • The Early Access Build Targets and Emulator match the latest Sailfish OS version released to Early Access users
  • By using the Early Access Build Targets and Emulator 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 > Build Targets > SailfishOS-ea-<arch>” and “Sailfish SDK > Emulators > SailfishOS-ea” 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

5 Likes