Re: [SailfishDevel] SDK again, again...
On Sunday, 17 November 2019 14.05.16 CET Thomas Tanghus wrote: > A picture says more... and so on: > > https://cloud.tanghus.net/apps/sharingpath/tanghus/Documents/SDK-installation.txt > > The "interesting" parts of the install log: > > https://cloud.tanghus.net/apps/sharingpath/tanghus/Pictures/Screenshots/SailfishOS/SailfishOS-SDK-kit-no-cmake.png And of course the links were supposed to be the other way around ;) -- /Thomas ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
Have you tried updating openssl on your laptop and reinstalling? Seems like this was the problem during install so it probably installed incorrectly? On Sunday, 17 November 2019, Thomas Tanghus wrote: > Apparently the SDK and I are not on the best of terms. > After having gotten it to work on my desktop PC, I am now trying to install > it on an older laptop. Every time I try to install it, I end up with a broken > kit, where cmake settings are missing/broken. Maybe because of: > > SOFT ASSERT: "kitInfo.isValid()" in file > ../../../../sailfish-qtcreator/src/plugins/qmakeprojectmanager/qmakeproject.cpp, > line 268 > > I have no idea whatsoever what to do from here without breaking more than I > fix. > > A picture says more... and so on: > > https://cloud.tanghus.net/apps/sharingpath/tanghus/Documents/SDK-installation.txt > > There were quite a few errors at the end of the installation. Among those: > - Device Sailfish_OS-Emulator-latest not found. > - Installing component Sailfish OS Build Target latest-i486 (3.2.0.12) > Integration for Sailfish OS IDE > Error: Id was not found. > - Installing component Sailfish OS Build Target latest-armv7hl (3.2.0.12) > Integration for Sailfish OS IDE > Error: Id was not found. > > The "interesting" parts of the install log: > > https://cloud.tanghus.net/apps/sharingpath/tanghus/Pictures/Screenshots/SailfishOS/SailfishOS-SDK-kit-no-cmake.png > -- > /Thoma -- Sent from my Jolla ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
On Sunday, 17 November 2019 14.29.11 CET szo...@gmail.com wrote: > Have you tried updating openssl on your laptop and reinstalling? Seems like > this was the problem during install so it probably installed incorrectly? Good suggestion, but I can't believe that to be the problem. It's a freshly installed Kubuntu 19.10 with an updated openssl: Package: openssl Version: 1.1.1c-1ubuntu4 Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1.282 kB Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1) -- /Thomas ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
Yeah, downgrading seems unlikely to fix it. Only other thing that comes to mind is the virtualization in bios: If the Emulator fails to boot to user interface, the reason might be disabled virtualization technology settings in host computer’s BIOS? But that should only impact emulator not the install so probably not it On Sunday, 17 November 2019, Thomas Tanghus wrote: > On Sunday, 17 November 2019 14.29.11 CET szo...@gmail.com wrote: > > Have you tried updating openssl on your laptop and reinstalling? Seems like > > this was the problem during install so it probably installed incorrectly? > > Good suggestion, but I can't believe that to be the problem. It's a freshly > installed Kubuntu 19.10 with an updated openssl: > > Package: openssl > Version: 1.1.1c-1ubuntu4 > Priority: important > Section: utils > Origin: Ubuntu > Maintainer: Ubuntu Developers > Original-Maintainer: Debian OpenSSL Team de...@lists.alioth.debian.org> > Bugs: https://bugs.launchpad.net/ubuntu/+filebug > Installed-Size: 1.282 kB > Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1) > > > -- > /Thomas > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.or -- Sent from my Jolla ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
Actually, downgrading to 1.0 might work as qtcreator 5.6 requires it according to https://forum.qt.io/topic/97098/install-qt-creator-5-6-0-on-ubuntu-mate-18-04-1/2 seems weird but could be worth a try and reupdating after install On Sunday, 17 November 2019, Thomas Tanghus wrote: > On Sunday, 17 November 2019 14.29.11 CET szo...@gmail.com wrote: > > Have you tried updating openssl on your laptop and reinstalling? Seems like > > this was the problem during install so it probably installed incorrectly? > > Good suggestion, but I can't believe that to be the problem. It's a freshly > installed Kubuntu 19.10 with an updated openssl: > > Package: openssl > Version: 1.1.1c-1ubuntu4 > Priority: important > Section: utils > Origin: Ubuntu > Maintainer: Ubuntu Developers > Original-Maintainer: Debian OpenSSL Team de...@lists.alioth.debian.org> > Bugs: https://bugs.launchpad.net/ubuntu/+filebug > Installed-Size: 1.282 kB > Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1) > > > -- > /Thomas > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.or -- Sent from my Jolla ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
On Sunday, 17 November 2019 15.24.18 CET szo...@gmail.com wrote: > Actually, downgrading to 1.0 might work as qtcreator 5.6 requires it > according to > https://forum.qt.io/topic/97098/install-qt-creator-5-6-0-on-ubuntu-mate-18-> > 04-1/2 seems weird but could be worth a try and reupdating after install Good find! It does look like it could at least solve the "cannot resolve" errors, I'm just baffled that no one else is having this problem? But how would one approach this. Preferably having both v.1.0 and v.1.1 side by side. Maybe it's possible to set an env variable saying which to use? I have no idea :P Hmm. Now I just checked my desktop PC. I has the same openssl version. I'll investigate some more. Thanks for the suggestions :) -- /Thomas ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
This has answer with some links: https://stackoverflow.com/questions/52210603/qt-and-openssl-incompatible-version-on-ubuntu Just download a 1.0 arm deb install, reinstall sdk, then apt-get update(?) to get back to latest (there is a compat package on fedora/opensuse according to this https://together.jolla.com/question/191318/problems-installing-sdk-1807-on-linux/ but didn't find a deb, so best to just downgrade for install and reupgrade after it seems) On Sunday, 17 November 2019, Thomas Tanghus wrote: > On Sunday, 17 November 2019 15.24.18 CET szo...@gmail.com wrote: > > Actually, downgrading to 1.0 might work as qtcreator 5.6 requires it > > according to > > https://forum.qt.io/topic/97098/install-qt-creator-5-6-0-on-ubuntu-mate-18-> > > 04-1/2 seems weird but could be worth a try and reupdating after install > > Good find! > > It does look like it could at least solve the "cannot resolve" errors, I'm > just baffled that no one else is having this problem? > > But how would one approach this. Preferably having both v.1.0 and v.1.1 side > by side. Maybe it's possible to set an env variable saying which to use? I > have no idea :P > > Hmm. Now I just checked my desktop PC. I has the same openssl version. I'll > investigate some more. Thanks for the suggestions :) > > -- > /Thomas > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.or -- Sent from my Jolla ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
Oops I wrote arm for some reason, just install std openssl 1.0 package for your laptop and if install works you're good to go (reupgrade to latest after, if you need 1.0 for running sdk, though that shouldn't be the case, you could just copy the .so's to sdk dir and have a small bash script to LD_PRELOAD relevant libs, but shouldn't be needed it seems only install requires 1.0) On Sunday, 17 November 2019, Thomas Tanghus wrote: > On Sunday, 17 November 2019 15.24.18 CET szo...@gmail.com wrote: > > Actually, downgrading to 1.0 might work as qtcreator 5.6 requires it > > according to > > https://forum.qt.io/topic/97098/install-qt-creator-5-6-0-on-ubuntu-mate-18-> > > 04-1/2 seems weird but could be worth a try and reupdating after install > > Good find! > > It does look like it could at least solve the "cannot resolve" errors, I'm > just baffled that no one else is having this problem? > > But how would one approach this. Preferably having both v.1.0 and v.1.1 side > by side. Maybe it's possible to set an env variable saying which to use? I > have no idea :P > > Hmm. Now I just checked my desktop PC. I has the same openssl version. I'll > investigate some more. Thanks for the suggestions :) > > -- > /Thomas > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.or -- Sent from my Jolla ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
Hi Thomas, The error messages in the tool tip shown when the *-armv7hl kit is hovered tell you the device selected in kit configuration is architecture incompatible with the kit. The kit supports armv7hl devices while the device (Sailfish OS Emulator) is an x86 device. You can still use the kit to build RPM packages for the armv7hl architecture, you will just not be able to run those directly from Qt Creator. For that you need to provide a hardware device with that architecture and configure the kit to use that instead of the emulator. Use the *- i486 kit if you want to run your software under the Sailfish OS Emulator. The installation log currently contains information that is mostly useful to someone with knowledge of SDK installer internals. An error message appearing there is not necessary meaning something wrong. The installer would complain verbosely if an installation error really occurred. The SSL-related errors are not likely to affect SDK functions regularly involved in Sailfish OS application development. BR, Martin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
Well the known issues page for SDK states: The installer does not handle all error conditions. But good to know openssl is not the culprit. On Monday, 18 November 2019, Martin Kampas wrote: > Hi Thomas, > > The error messages in the tool tip shown when the *-armv7hl kit is hovered > tell you the > device selected in kit configuration is architecture incompatible with the > kit. The kit > supports armv7hl devices while the device (Sailfish OS Emulator) is an x86 > device. You can > still use the kit to build RPM packages for the armv7hl architecture, you > will just not be > able to run those directly from Qt Creator. For that you need to provide a > hardware device > with that architecture and configure the kit to use that instead of the > emulator. Use the *- > i486 kit if you want to run your software under the Sailfish OS Emulator. > > The installation log currently contains information that is mostly useful to > someone with > knowledge of SDK installer internals. An error message appearing there is not > necessary > meaning something wrong. The installer would complain verbosely if an > installation error > really occurred. > > The SSL-related errors are not likely to affect SDK functions regularly > involved in Sailfish > OS application development. > > BR, > Martin > -- Sent from my Jolla ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
Sorry if this mail comes several times. Had some problems with kmail. On Monday, 18 November 2019 07.34.25 CET you wrote: > Hi Thomas, > > The error messages in the tool tip shown when the *-armv7hl kit is hovered > tell you the device selected in kit configuration is architecture > incompatible with the kit. The kit supports armv7hl devices while the > device (Sailfish OS Emulator) is an x86 device. You can still use the kit > to build RPM packages for the armv7hl architecture, you will just not be > able to run those directly from Qt Creator. For that you need to provide > a hardware device with that architecture and configure the kit to use > that instead of the emulator. Use the *- i486 kit if you want to run your > software under the Sailfish OS Emulator. Thanks a lot for the detailed explanation, and sorry for the late reply. I got access to my desktop pc, and got side-tracked elsewhere. I will try to install again on my laptop. I was sure I had set the kit to arm and the device to run on to be my phone, but you're right that it doesn't look like it in the screenshot. > The installation log currently contains information that is mostly useful > to someone with knowledge of SDK installer internals. An error message > appearing there is not necessary meaning something wrong. The installer > would complain verbosely if an installation error really occurred. Good to know, I'll focus on the relevant parts. -- /Thomas ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SDK again, again...
Thomas Tanghus wrote: > Apparently the SDK and I are not on the best of terms. > After having gotten it to work on my desktop PC, I am now trying to > install it on an older laptop. Every time I try to install it, I end up > with a broken kit, where cmake settings are missing/broken. Maybe because > of: I am not sure but I think I had the same or very similar issue here. Everytime I did installation and modified the settings in the installer it finished with broken installation. For example I want to have only the build engine for the latest two releases. I had to uninstall and install several times to get it right. I don't recall anymore the details, but I think using the tool after installation did break things. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
