Thanks,
it worked fine when I added to running part the alternative command:
invoker --type=silica-qt5 -s /usr/bin/harbour-myapp
2014-07-12 21:55 GMT+03:00 Andrey Kozhevnikov :
> you should start silica app with invoker
>
> 13.07.2014 00:10, Jukka Heikkilä пишет:
>
> Hi folks!
>
> During dev
you should start silica app with invoker
13.07.2014 00:10, Jukka Heikkilä ?:
Hi folks!
During developing my program I have mostly used Emulator to run the
app and sometimes also real device and testing has been worked fine on
both. Now I faced the next problem with real device. When I pre
Hi folks!
During developing my program I have mostly used Emulator to run the app and
sometimes also real device and testing has been worked fine on both. Now I
faced the next problem with real device. When I press run from Qt Creator,
it will normally compile the app and transfer it to real devic
On Monday 07 July 2014 20:37 Robin Burchell wrote:
> This might sound strange and all, but do realize that we are probably one
> of the most extensive users of the Qt stack (in that we literally use
> pretty much all of it) and certainly one of the most extensive users of
> QtQuick & QML. We¹re a
And btw. even after fixing the permissions, VirtualBox comes with the
following error:
Failed to open a session for the virtual machine SailfishOS Emulator.
The VM session was closed before any attempt to power it on.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface
Why do the mersdk/MerSDK and emulator/SailfishOS Emulator directories have
700 permissions? It makes the VMs unaccesible.
--
Marcin
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
