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
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
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
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
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,
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
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
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
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:
>
>
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:
IMO this shoud not be a problem
вс, 17 нояб. 2019 г. в 01:33, E.S. Rosenberg <
es.rosenberg+sailfishos@gmail.com>:
> Would picture-in-picture that shows on other screens even make it through
> Jolla QA?
>
> Op za 16 nov. 2019 om 21:37 schreef Андрей Кожевников <
> coderusin...@gmail.com>:
>
11 matches
Mail list logo
