On Thursday, 30 April 2020 12.49 Martin Kampas wrote:
> Today (Apr 30th) at 10:00 UTC the Sailfish SDK 3.1 was released to Early
> Access users. Please, check out the release notes from
> https://together.jolla.com/question/226423/[1] .
> 
> The installers for this SDK release are now available at
> https://sailfishos.org/wiki/
> Application_SDK_Early_Access#Latest_Early_Access_SDK_Release[2] . If you
> have an older Early Access release of the SDK installed, you should see
> an update notification in the Sailfish IDE.

I first tried the online installer, but the repository couldn't be found. 
The offline installer succeeded, but it seems Clang is having problems:

~/SailfishOS/lib/qtcreator/plugins/libClangTools.so: Cannot load library /
home/thomas/SailfishOS/lib/qtcreator/plugins/libClangTools.so: (libtinfo.so.
5: cannot open shared object file: No such file or directory)

I have libtinfo.so.5 installed, but not in /usr/lib

$ locate libtinfo.so.
/snap/core/9066/lib/x86_64-linux-gnu/libtinfo.so.5
/snap/core/9066/lib/x86_64-linux-gnu/libtinfo.so.5.9
/snap/core18/1705/lib/x86_64-linux-gnu/libtinfo.so.5
/snap/core18/1705/lib/x86_64-linux-gnu/libtinfo.so.5.9
/snap/core18/1754/lib/x86_64-linux-gnu/libtinfo.so.5
/snap/core18/1754/lib/x86_64-linux-gnu/libtinfo.so.5.9
/usr/lib/x86_64-linux-gnu/libtinfo.so.6
/usr/lib/x86_64-linux-gnu/libtinfo.so.6.1

libtinfo5 is in Ubuntu 19.10 described as "legacy version", so maybe the SDK 
should link against a newer version; at least when Ubuntu 20.04 LTS is 
released. Isn't it by now, btw?

Anyways, I installed the legacy version and it seems to work, but I don't 
even know what Clang does to start with ;)
 
-- 
Med venlig hilsen / Best regards

Thomas Tanghus

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Reply via email to