We have moved to a new Sailfish OS Forum. Please start new discussions there.

SDK on Windows 7 x64

asked 2015-10-26 17:55:21 +0300

Joerg gravatar image

Hi everyone!

I have installed the SDK using https://sailfishos.org/develop/sdk-overview/develop-installation-article/ on a Windows 7 x64 (German) machine. While QtCreator is running and I can create myfirstapp. I have problems compiling and running the application:

  • in myfirstapp.qml: ApplicationWindow is underlined and says "Could not resolve the prototype 'Window' of 'ApplicationWindow' (M301)."
  • I can not run the SDK VM ("No virtual machine with the name "MerSDK" found ...')
  • I can not run the Emulator VM ('No virtual machine with the name "SailfishOS Emulator" found ...')

I installed:

  • VirtualBox 4.3.32r10443 (as Administrator)
  • Visual C++ 2010 redistributable for x86 (as Administrator)
  • SailfishOSSDK-Beta-1510-Qt5-windows-offline.exe (as regular user)

I pretty much only clicked through the setup. So

  • VirtualBox is in C:\Program Files\Oracle\VirtualBox
  • SailfishSDK in C:\SailfishOS

If I check with VirtualBox Manager it has the two VMs

  • MerSDK in C:\SailfishOS\mersdk\MerSDK
  • SailfishOS Emulator in C:\SailfishOS\emulator\SailfishOS Emulator

What can I do to make the IDE find it's files?

Thanks, Jörg

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted

answered 2015-10-26 21:26:33 +0300

rweickelt gravatar image

The SDK tries to launch VBoxManage in order to start a VM. This seems to fail in Your case. It might be enough to set the environment variable VBOX_INSTALL_PATH or VBOX_MSI_INSTALL_PATH accordingly. Here is a link to the code that resolves the VBoxManage binary (line 70-87).

You can check, whether virtualbox works from command line by typing C:\PATH_TO_VBOX\VBoxManage list vms. I don't think, that You have to re-install vbox as local user.

Good luck.

edit flag offensive delete publish link more


Thank you! This solves the problem.

I'm not sure if VirtualBox really needs to be installed as Administrator. My actual problem was, that the VBOX_MSI_INSTALL_PATH was written to the system profile. That is only updated for regular users after a reboot. So actually rebooting solved my problem.

Maybe if VirtualBox (can be) is installed as user, the problem would not appear. I think, if someone has tried that, she can comment here, so the next one knows.

Thanks again, for your help.

Joerg ( 2015-10-26 22:12:44 +0300 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2015-10-26 17:55:21 +0300

Seen: 540 times

Last updated: Oct 26 '15