Update History
- 2021-06-02 Sailfish SDK 3.5 released to Early Access users
- 2021-06-10 Sailfish SDK 3.5 released to all users
- 2021-09-03 Early Access Build Targets updated to 4.2.0.19 (Verla)
Most notable changes included in this release:
- Qt Creator upgraded to 4.14.2
- RPM package signing support
Contributions from Aurora SDK and the developer community
Here are some of the features contributed by Open Mobile Platform to the Sailfish SDK:
- RPM package signing support
- Bug fix: Selecting a different Device does not change the Run configuration
- Bug fix: Long url in Rpm Validation suites overlaps the suites name in Sailfish SDK deploy step
We would also like to thank the people who have reported bugs via forum.sailfishos.org.
Release Content
The latest Emulator and Build Targets match the Sailfish OS release 4.1.0 “Kvarken”
SDK IDE (Qt Creator)
- Qt Creator upgraded to 4.14.2
- On Windows we now ship 64 bit binaries - 32 bit Windows is no longer supported
- Bugs fixed:
- Selecting a different Device does not change the Run configuration
- Long url in Rpm Validation suites overlaps the suites name in Sailfish SDK deploy step
- Extra dot/dotdot components in sfdk path in compile output
- Build continues running on background when stopped from Qt Creator
- Sailfish SDK suggests “import QtQml 2.3” even though it is not available on device
- Cannot deploy new public SSH key to added device
- Qt Creator offers user home instead of SDK workspace as the default destination for projects
- Some actions under Qt Creator invoke sfdk outside of SDK workspace
- Qt QmlLive does not work with aarch64 devices
- Qt Creator allows to use an aarch64 device with an armv7hl kit an vice versa
- The “Executable on device” field uses backslashes on Windows (CMake)
- Qt Creator tries to list Docker images on installation with VBox-based build engine
SDK CLI (sfdk)
- Generating qmltypes files (see
sfdk qmltypes --help
) - Possibility to dry run deployment
sfdk deploy --dry-run
- Removing snapshots of a target
sfdk tools remove --snapshots-of
- Bugs fixed:
- Cannot pipe output to/from commands executed on build engine and devices
- Emulator is not started automatically for the ‘deploy’ command
- Inaccurate reverse path mapping
- Build target snapshot is not reset after changing SSU configuration of the original target
- sfdk fails to list build tools with 2nd level and deeper snapshots
- ‘sfdk tools list’ hangs when SDK updates are available
Emulator
- Bugs fixed:
- syslinux-extlinux: post scriptlet fails under emulator
- Sailfish OS Emulator 3.4.0.24 unusable under Sailfish SDK 3.4
Build Engine
- Aarch64 targets preinstalled
- Progress is now displayed when installing build time dependencies
- build target snapshots as lightweight copies when possible
- Currently this means combination Linux + Docker build engine + btrfs as host filesystem
- Bugs fixed:
- Build target snapshot is not reset after changing SSU configuration of the original target
- Zypper failure is completely ignored when updating SDK objects
- Assertion failure when updating SDK objects: name not valid
- sdk-manage outputs help to stderr which is cumbersome to grep
- RPM validation output polluted with BASH syntax error about bad use of “continue” keyword
- Older build targets available from repositories cannot be installed
General
- RPM package signing support
- Installer now creates manually entered workspace paths if they don’t already exist
- PageStack animatorPush() in application templates
- Bugs fixed:
- GDB unusable on Arch Linux - incompatible libncurses.so.5
- Qt Creator and sfdk never tries to soft-close VMs
- Build tools scripts are recreated unconditionally on sfdk/qtc startup
- Build tools cannot be installed/removed after changing workspace path later after installation
- SailfishOS/emulator: Directory not empty
- devices.xml not created after SDK re-installation
- SDK with Docker on Windows: installation fails after long time if docker is not running
- Docker based SDK installation doesn’t fail gracefully when docker is installed but unusable
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