Update History
- 2021-11-24 Sailfish SDK 3.7 released to Early Access users
- 2021-12-01 Sailfish SDK 3.7 released to all users
Most notable changes included in this release:
The biggest changes in this release are new features in our command line tool, sfdk:
- sfdk command autocompletion under bash
- sfdk help is now rendered as man pages, making it easier to read
As these features rely on functionality of the underlying shell, i.e. bash, starting from this release we recommend that Windows users use MSYS2 shell instead of Git bash. Similarly, macOS users will only see these features if they use newer bash and bash-completion packages e.g. from Homebrew. Please find more information in the documentation.
With this Sailfish SDK release, the recommended Linux OS environment changes to Ubuntu 20.04.
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.3.0 “Suomenlinna”
SDK IDE (Qt Creator)
- Default device user name changed from “nemo” to “defaultuser”
- Amber Web Authorization documentation
- Bugs fixed:
- The popup offering to run qmake in order to detect possible additional arguments is annoying
- SDK validates debugsource package instead of application package
- Code model text in options dialog should be wrapped
SDK CLI (sfdk)
- sfdk command autocompletion under bash
- sfdk help is now rendered as man pages, making it easier to read
- Bugs fixed:
- sfdk engine exec: Random failure with build engine initially stopped
- sfdk: no reverse path mapping for system headers in build output
- SDK doesn’t use --with argument correctly when resolving dependencies
- sfdk: emulator is not started automatically with the --rsync deployment method
- sfdk is not accurate when listing configuration options related to a command
- sfdk: available build target names are not completed
General
- Added Nemo.Keepalive to cameragallery example
- Bugs fixed:
- qmake warns about __fxstatat64()
- qtc-support is installed in build engine
- qmake installs libs to /usr/lib/ on aarch64 targets, and the builds fail
- Docker-based build engine: no feedback on naive instantiation of the image
Installation/Maintenance
- Bugs fixed:
- SDK installer on Windows requires git on PATH
- Custom build targets remain listed by SDK Maintenance Tool after SDK upgrade
- SDK Maintenance Tool silent for too long when stopping Docker-based build engine
- Sailfish SDK installer sets SFDK_AUTO_STOP_VMS env variable persistently on Windows
Known Issues
- rpmlint validation suite doesn’t work on 4.3.0.12 targets
- Please see Sailfish SDK Known Issues for a full list of known issues, more information and a workaround for the abovementioned issue
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