Hi Marcin
That is black and white confirmation that the SDK VM is not installed.
You mentioned an earlier alpha. My (educated?) guess is that a remnant
of that was still around when you installed the latest SDK.
Maybe you should a complete (yes complete) deinstall, then reinstall.
My experience is that before upgrading you need to deinstall, then
hunt all out all the hidden directories and remove those (.scratchbox2
etc.). If you search the archives of this mailing list you will find
reference to them.
Upgrading a Sailfish SDK reminds me just a little of upgrading Oracle
on Windows: hunting and eradicating every trace in the file system and
registry before install the new version ...).
Now I need to get a loaf of bread out of the oven ... It's smelling good!
Grüsse
Chris
Zitat von "Marcin M." <marmistrz...@gmail.com>:
I'm using simply virtualbox-4.3 from the official repo:
$ apt-cache policy virtualbox-4.3
virtualbox-4.3:
Installed: 4.3.6-91406~Ubuntu~raring
Candidate: 4.3.6-91406~Ubuntu~raring
Version table:
*** 4.3.6-91406~Ubuntu~raring 0
500
http://download.virtualbox.org/virtualbox/debian/saucy/contrib
amd64 Packages
100 /var/lib/dpkg/status
4.3.0-89960~Ubuntu~raring 0
700 http://packages.linuxmint.com/ petra/import amd64 Packages
$ vboxmanage list vms
"WinXP" {4bfb163e-8537-470b-81ac-542629875e44}
"SailfishOS Emulator" {10d6d122-6581-42da-b6e0-562266fced05}
vboxmanage list runningvms shows nothing
--
Marcin
2014/1/1 <christopher.l...@thurweb.ch>
marcin
What do the following commands give you (in a terminal)'
vboxmanage list vms
vboxmanage list runningvms
The first should show installed VMS, the second those currently running.
You may also have the Virtualbox-qt gui installed somewhere giving similar
info.
Grüsse
Chrsi
Zitat von "Marcin M." <marmistrz...@gmail.com>:
Hi,
Thanks, it was a (partial) fix.
Now, when trying to build, I get:
Virtual Machine 'MerSDK' is not installed!
--
Marcin
2014/1/1 <christopher.l...@thurweb.ch>
Hi Marcin
The project templates have changed quite a bit since then, and I am
fairly
sure I have seen the same behaviour.
Try a new default project.
If that works, then you can copy across your c++ / qml files from your
alpha project into the new default project.
Chris
Zitat von "Marcin Mielniczuk" <marmistrz...@gmail.com>:
Well, I should've said it more precisely :) - I open a project created
by
the first alpha. I click the emulator button. It grays out, nothing
happens.
--
Sent from my Nokia N900
Marcin
On Wed Jan 1 15:56:45 2014 christopher.l...@thurweb.ch wrote:
Marcin
Do you have a project open? The Emulator and SDK launch buttons remain
grey until you do
Chris
Zitat von "Mikael Hermansson" <m...@7b4.se>:
> That should work, I have it in opt and have no problem.
>
> Looks more like you have an issue with you project file?
>
> check the compile output/message screen if you get qmake errors or
> similar?
>
> also try build->clean all.
>
>
> On Wednesday 01 January 2014 11.12.58 Marcin M. wrote:
> > Hi,
> >
> > I've installed the SDK into /opt, but I'm unable to launch the
> > emulator nor the SDK VM - only the buttons are grayed out. Is there
> > a known workaround, so that I can avoid reinstalling into
> > /home/$USER/ ?
> >
> > thanks
> > --
> > Marcin
>
> --
> Skickat från Lenovo Thinkpad X230 running Kubuntu desktop
> _______________________________________________
> SailfishOS.org Devel mailing list
>
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
