[release notes] Sailfish SDK 2.3 [not a question]
Sailfish SDK version 2.3
Today (Nov 6th) at 14:00 UTC we published new installers and repositories of the Sailfish SDK to all users. This SDK release is called 2.3 and it enables development for Sailfish OS release 3.2.0.
Important! If you are an Early Access SDK user, please read the following notes:
- The method of subscribing to Early Access updates changes with this release
- Users currently subsribed to Early Access updates (using the older method) must unsubscribe first!
- This is done by removing the two
*-ea
repositories and enabling the default repositories again - After the initial upgrade finishes, it is possible to subscribe to Early Access updates using the new method described below
- This is done by removing the two
- Subscribing to EA updates is done by enabling the
updates-ea
repository. Please read the detailed Early Access SDK installation or update instructions - Instructions for adding the early access repository into the SDK can be found from the Early Access SDK wiki page
If you have an older release of the SDK, you should see an update notification in the Sailfish IDE.
- During this update, you might get a warning about a failed
rmKit
operation while installing the update. It can be safely ignored.
The latest Emulator and Build Targets match the Sailfish OS release 3.2.0.12 (Torronsuo)
Emulators and Build Targets for several older Sailfish OS releases remain available.
A couple of things you should be aware of:
- Git is a prerequisite for the Sailfish SDK on Windows - you can get Git from https://git-scm.com/download/win, if it is not already installed on your workstation.
- As before, in this update the Build Engine, Emulator and Targets are reinstalled so you will lose all changes you may have made in those. However, if your application packaging is done correctly, rebuilding your projects should reinstall the packages you have been using.
- Any customization done to SDK (adding new package repositories, adding custom Targets, additional source paths) will be removed during the installation process so make your own backup of those before starting the update.
- If you import existing projects made with a previous version of the SDK, make sure to select the correct kit in the project configuration step. Both ARM and i486 kits are available.
- Package repository contents have been updated and consequently using a previous SDK version with these package repositories is not supported.
- For more information, please see the Application SDK known issues list.
Release Content
Sailfish SDK 2.3
Emulator
- Unnecessary packages removed (these can still be installed via pkcon if needed):
- vim-filesystem
- vim-enhanced
- vim-common
- tar (there is busybox tar, if you need gnu version you can install it via pkcon)
- python-libs
- python3-gobject
- python3-base
- python
- pygobject2
- ofono-tests
- mce-tools
- libpython3_7m1_0
- libngf-client
- libaccounts-glib-tools
- gobject-introspection
- gdb
- dbus-python3
- dbus-python
- cpio (there is busybox cpio, if you need gnu version you can install it via pkcon)
- connman-test
SDK IDE (Qt Creator)
- Nemo-keepalive documentation available in help mode
Installer/Maintenance Tool
- The method of subscribing to Early Access updates changed
- Starting with this release it is possible to turn off regular updates as well
- This does not change the fact that only the latest SDK release is officially supported
If you have any questions, feel free to either send an email to SailfishDevel mailing list: devel at lists.sailfishos.org, write it up here in http://together.jolla.com and tag your issue with 'sdk' or send an e-mail to developer-care at jolla.com.
Happy hacking,
Jolla SDK Team
Sorry probably really dumb question but where is the SDKMaintenanceTool? I have installed the 2.2 version recently, don't think it was EA version but not sure. So trying to find where to disable the ea repositories. Btw is it just me, but last time I have played with the SDK (was during sfos 2.0) running code in the emulator was waaaay faster, not sure if some config issue, but it used to be like 10-20s from click on build/run to have it in the emulator, now it takes like a minute or two, is that because of the intel bugs, or???
szopin ( 2019-11-07 16:08:03 +0200 )editIt is quite good question, or two at least, and as such they should be posted as questionS, not as a comment. Please submit them as questions. Looking forward to answering them :)
martyone ( 2019-11-07 16:18:10 +0200 )editOk, one sec, thought it was me just being dumb
szopin ( 2019-11-07 16:25:37 +0200 )edit@martyone found the SDK Maintenance Tools after upgrade to 2.3 from Help->Check for Updates, if you have any fixes for the long deploy times the question is open at https://together.jolla.com/question/216248/latest-sdk-buildrun-taking-a-lot-longer-than-it-used-to/ thanks!
szopin ( 2019-11-07 18:11:25 +0200 )edit