Problems installing SDK 1807 on Linux
asked 2018-10-24 20:09:10 +0300
A couple of problems installing SailfishOSSDK-Beta-1807-Qt5-linux-64 on OpenSuSE Leap 15
1 Installer outputs many lines like this:
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
Googling similar messages I think this may be because I have openssl 1.1 and it wants 1.0 - but that might be wrong. What effect this has on development I don't yet know.
2 During installation it invites me to 'Specify the directory where the OS SDK will be installed' So I put in ~/david/apps/SailfishOS
But this fails because the SDK still assumes the default ~/david/SailfishOS for some stuff. When I run it:
No tool chain set up in kit "Desktop" for "C++".
No tool chain set up in kit "Desktop" for "C++".
Targets file not found: "/home/david/SailfishOS/mersdk/targets/targets.xml"
This will remove all installed targets for "Sailfish OS Build Engine"
And when I load the example python project I get:
Load python example
Configure project
No valid kits found
I reinstalled with the default locations and the kits appeared.
I'll raise these as issues in github if somebody tells me where.
Will there be a new SDK for SFOS 3? If so I might wait for it.
Continued...
Bug 2 is easily overcome by adding a symlink: ~/SailfishOS -> /home/david/apps/SailfishOS
'Connecting to the "Sailfish OS build engine" virtual machine' - fails.
~/.xsession-errors shows
MerConnection: "Failed to establish SSH conection with virtual machine \"Sailfish OS Build Engine\": 5 Private key file error: No such file or directory"
Is this the result of the first problem - with qt.network.ssl?
Later
I overcame the keys problem by generating and authorising keys in options>Sailfish OS>Build engine
Hit the same problem with the emulator. Generated keys for that in options>devices>devices>Sailfish OS emulator
I don't know if those keys should have been generated by the install, and whether that's because of the qt.network.ssl problem.
Anyway, I can build the python example and run the rpm on my Jolla-C - so I guess that's a success.
Maybe you want to check out https://together.jolla.com/question/158742/sailfish-sdk-container-on-docker-hub/ meanwhile.
bomo ( 2018-10-25 18:45:29 +0300 )Hi, I had similar problems under Ubuntu (see https://together.jolla.com/question/191219/install-sdk-in-non-standard-path-no-available-kits-found/). Installing everything at the default location fixed it for me. Keys were generated automatically in this case, too. I didn't have the SSL problem, though.
Mario ( 2018-10-26 21:24:21 +0300 )Thx. Is that also with 64bit v1807? What version of openssl do you have?
DaveRo ( 2018-10-26 23:34:08 +0300 )Using non-standard installation path is broken currently, as already discovered by Mario.
Installing to the standard installation path will not fix the SSL related warnings. Considering that you could finish the installation they should not be fatal.
martyone ( 2018-10-29 09:06:39 +0300 )