The Following 2 Users Say Thank You to w00t For This Useful Post: | ||
![]() |
2013-10-25
, 15:12
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#222
|
[nemo@SailfishEmul ~]$ cat /etc/os-release NAME=SailfishOS ID=sailfishos VERSION=0.98.0.67 VERSION_ID=0.98.0.67 PRETTY_NAME="SailfishOS 0.98.0.67 (i486,testing)" SAILFISH_BUILD=67 SAILFISH_FLAVOUR=testing HOME_URL="https://sailfishos.org/"
![]() |
2013-12-13
, 12:15
|
Posts: 1,269 |
Thanked: 3,961 times |
Joined on May 2011
@ Brazil
|
#223
|
Hello again,
Today at 14:00 UTC we will publish new installers, package repositories and updated website documentation for our SailfishOS SDK version Alpha-1312-Qt5.
If you already have an existing Alpha-Qt5 SDK installed you should see updates available icon in Qt Creator. If you don't have it installed, you can get the latest installer from www.sailfishos.org<http://www.sailfishos.org>. It is recommended to uninstall the old SDK and download a new installer.
This update brings the long-awaited Mer ARM device support to Qt Creator and fixes issues with the application template regarding requirements for Harbour submissions. Qt Creator Sailfish kits now also support shadow building, which separates the different architecture builds from each other negating the need to always clean the build directory when switching between ARM and i486 kits.
A couple of things you should be aware of:
- Like before, in this update the build engine, emulator and targets are re-installed 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.
- All 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 Sailfish OS SDK, make sure you select the correct kit in the project configuration step. Both ARM and i486 kits are available.
- Windows users need to install VC10 runtime from http://www.microsoft.com/en-us/downl...n.aspx?id=8328 or Installer will ask for admin rights during installation.
- Package repository structure on SailfishOS.org has changed to be closer to the released Jolla phone repositories, so previous SDK installations will not work.
- For more information, please see SDK Alpha-Qt5 known issues list at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
Here are the release notes of this update.
Installer:
* Setting the additional application source folder now actually works. This setting can be used to specify a project location that is outside of your home directory.
SailfishOS SDK IDE:
* Qt Creator updated to version 2.8.1-3
* Qt Creator uses new wizard to create Mer ARM device, device creation is described on https://sailfishos.org/develop-firstapp-article.html in section 'Create a connection to Mer ARM device'
* Shadow building is supported, you can now safely build applications for both architectures without them clashing.
* Shadow building is on by default for each new project, but can be turned off in project's settings.
* Latest SDK Application template is integrated so Harbour application requirements can be more easily fulfilled.
* User settings are now stored in a new directory (Linux/OSX: $HOME/.config/SailfishAlpha3, Windows:C:\users\username\AppData\Roaming\Sailfish Alpha3) so deleting old settings directory is not mandatory.
Templates/examples/tutorials
* Templates are updated with the latest SDK Application template.
* Quite a few Qt5 tutorial applications were ported to Sailfish OS, they can be found from ~/SailfishOS/tutorials and they can be used to study Sailfish OS application behaviour. Each tutorial's project directory has a README.md file which contains notes from a developer when porting the application from Desktop QML to Sailfish OS. Some of the notes might be outdated.
SDK Maintenance Tool:
* Installer version updated to 1.4.0-2.
Documentation:
* Documentation is updated with latest available versions. Documentation may contain references to Qt 5.0 - please see known issues list at: https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues.
Build Engine:
* Shadow building creates separate build directories outside your project directory named build-PROJECTNAME-KITNAME-[Debug|Release]
* The RPM packages for your project are also created under the shadow build directory
* Build Engine will not treat missing qtc_ macros in spec file as fatal.
SailfishOS Emulator:
* Emulator software is updated to match Jolla Phone release 1.0.1-10 "Laadunjärvi".
* SSH login password for nemo user can be set with Developer settings in Settings application.
* Package repositories can be refreshed with Developer settings in Settings application.
* Icon sizes are matched to Harbour requirements.
SailfishOS Targets:
* Both i486 and ARM target builds based on updated Jolla baseline.
If you encounter any issues, please report them to Sailfish developers mailing list at devel at lists.sailfishos.org
Happy hacking,
The Jolla SDK Team
![]() |
2013-12-13
, 14:32
|
Posts: 1,269 |
Thanked: 3,961 times |
Joined on May 2011
@ Brazil
|
#224
|
The Following 3 Users Say Thank You to rcolistete For This Useful Post: | ||
![]() |
2013-12-13
, 20:03
|
Posts: 1,269 |
Thanked: 3,961 times |
Joined on May 2011
@ Brazil
|
#225
|
The Following 4 Users Say Thank You to rcolistete For This Useful Post: | ||
![]() |
2013-12-13
, 21:18
|
|
Posts: 634 |
Thanked: 3,266 times |
Joined on May 2010
@ Colombia
|
#226
|
![]() |
2013-12-14
, 06:02
|
Posts: 2,076 |
Thanked: 3,268 times |
Joined on Feb 2011
|
#227
|
I'm curious as to why the the SDK is still considered to be "Alpha" despite the fact the Jolla device is now available. What else do they plan to chop and change? Is the Silica API considered to be stable?
![]() |
2013-12-14
, 08:43
|
|
Posts: 7,075 |
Thanked: 9,073 times |
Joined on Oct 2009
@ Moon! It's not the East or the West side... it's the Dark Side
|
#228
|
I'm curious as to why the the SDK is still considered to be "Alpha" despite the fact the Jolla device is now available. What else do they plan to chop and change? Is the Silica API considered to be stable?
![]() |
2013-12-14
, 14:18
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#229
|
![]() |
2013-12-15
, 17:09
|
Posts: 1,269 |
Thanked: 3,961 times |
Joined on May 2011
@ Brazil
|
#230
|
The Following 3 Users Say Thank You to rcolistete For This Useful Post: | ||
You could always try build it yourself, for fun:
https://github.com/nemomobile/ngfd/c...a980a1f007aba5
should be the fix for this...
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.