Ask / Submit
9

SDK version 1804 released

asked 2018-06-06 18:37:18 +0200

martyone gravatar image

updated 2018-06-08 18:02:05 +0200

Hello,

Today (Jun 8th) the 1804 SDK release was made available to all users.

If you have an older beta release of the SDK, you should see an update notification in the Sailfish OS IDE. View more information in the SDK wiki page and also check out the known issues page.

Happy hacking!


6.6.2018

The Sailfish OS SDK update 1804 has been released to Early Access. This update has the latest 2.2.0.29 build environment, which matches the Jolla Release 2.2.0 (Mouhijoki). It also contains lots of bugfixes and adds the ability to change the SSH and HTTP ports used by the SDK Build Engine and Emulator. Find out more about these features and the release content from the release notes.

Note for Early Access users:

It was discovered only after publishing the installers and repositories to Early Access, that the build Targets included in the Early Access release were corrupted.

This was fixed on Thursday, Jun 7, at 12:00 UTC. If you installed/upgraded to version 1804 before that time, you can fix your installation with these steps:

  • Start Qt Creator and switch to the Sailfish OS mode (Control Centre)
  • Remove the two preinstalled build Targets (SailfishOS-2.2.0.29-armv7hl and SailfishOS-2.2.0.29-i486). Remove just the Targets, preserve the Tooling
  • Install the Targets again using the controls below

Apologies for the inconvenience.

edit retag flag offensive close delete

Comments

2

When I type a mb2 -t ... build command in the build engine, connected via ssh, I got: Warning: No repositories defined. Operating only with the installed resolvables. Nothing can be installed. and operation fails because of missing dependencies. Is there a new procedure to follow?

Damien Caliste ( 2018-06-06 19:14:50 +0200 )edit

@damien Same here :(

Dylan Van Assche ( 2018-06-06 20:20:08 +0200 )edit
2

@damien-caliste @dylan-van-assche That's bad. A hardware error (as it seems) caused that the SDK build targets were corrupted during build. Since it was the very last RC with very limited changes, it was also not discovered by testing. Fix ongoing.

martyone ( 2018-06-07 10:01:51 +0200 )edit

@martyone no problem, thanks for the fix, will test this evening. After all EA is used for this also.

Damien Caliste ( 2018-06-07 15:22:42 +0200 )edit

@martyone, indeed the problem has been fixed. Following the steps above allow to compile again. Thank you.

Damien Caliste ( 2018-06-07 21:18:57 +0200 )edit

1 Answer

Sort by » oldest newest most voted
5

answered 2018-06-06 20:09:47 +0200

RPM validator isn't updated yet?

ERROR [/usr/share/harbour-sailfinder/qml/components/MessagingBar.qml] Import 'QtFeedback 5.0' is not allowed

QtFeedback 5.0 is allowed from 2.2.0 and above (see Github)

Hardcoded paths in translation strings shouldn't be marked as 'hardcoded'

ERROR [/usr/share/harbour-sailfinder/qml/pages/TermsPage.qml] Hardcoded path: //% "%0 keeps a minimalistic log in /home/nemo/.cache/%1/logging/log.txt for debugging purposes.

This is used for a translation string using ID's. The regex shouldn't check strings starting with //%.

edit flag offensive delete publish link more

Comments

Unfortunately the change to RPM validator was not delivered to 2.2.0. Please repost your question on hardcoded paths as a question.

martyone ( 2018-06-13 09:29:49 +0200 )edit

@martyone I will post it as a question. I didn't received a notification about your comment.

Dylan Van Assche ( 2018-08-20 20:53:29 +0200 )edit
Login/Signup to Answer

Question tools

Follow
4 followers

Stats

Asked: 2018-06-06 18:37:18 +0200

Seen: 582 times

Last updated: Jun 08 '18