If someone finds it useful, I wrote a dummy version of the OSX guide for
persons such as me, who are not very seasoned with VirtualBox:
http://matrixxreloaded.wordpress.com/2013/03/05/how-to-install-sailfishos-sdk-on-osx-the-dummy-guide/
- Saija
Lähetetty iPadista
"Saija Eteläniemi" <setel...@live.com> kirjoitti 5.3.2013 kello 13.48:
> Actually I already tried many times to press "yes" when QtCreator offered to
> start the emulator, even though I knew it has no effect. It didn't make
> QtCreator satisfied with any of those attempts.
>
> Then a miracle happened, I tried again today, pressing "yes" multiple times,
> and trying out different combinations of commands (build, rebuild, deploy,
> run, debug), and suddenly it started working! Now I'm never gonna shut down
> any part of the setup to not break it again :D
>
> Thanks for the SDK, and the instructions for Mac, I'm a very happy camper :)
>
> - Saija
>
> Lähetetty iPadista
>
> martin.gri...@gmail.com kirjoitti 5.3.2013 kello 8.45:
>
>> Hi,
>>
>> I have also seen thr message that the emulator was not running a couple of
>> times. QtCreator asked me if I want it to start the emulator, so I said
>> "yes". That is a no-op anyway (since VBoxManage was replaced), but if it
>> makes QtCreator happy... ;)
>>
>>
>> Martin
>>
>> Saija Eteläniemi schrieb am 04.03.13 21:21:
>>
>> I got one step further. The reason why QtCreator didn't find the the
>> simulator was that I forgot to give the VBoxManage script executable rights.
>> Now I can connect to the device, and test says device successfully connected.
>> If I actually try to deploy my project (default hello) on the device it says
>> SailfishOS Emulator is not running, which is weird since the device test
>> went fine. Tried to restart QtCreator several times, and also re-recorded
>> the outputs of the VBoxManage commands, but no help there. Any tips to
>> share, or should I start the rubberhose debugging now? :)
>>
>> - Saija
>>
>> Lähetetty iPadista
>>
>> "Saija Eteläniemi" <setel...@live.com> kirjoitti 4.3.2013 kello 21.33:
>>
>> > Thanks,
>> >
>> > Silly me, back to the drawing board then. I'll save the VBoxManage outputs
>> > again, to make sure they are correct, and see if I manage to fix the
>> > problem.
>> >
>> > - Saija
>> >
>> > Lähetetty iPadista
>> >
>> > "Martin Grimme" <setel...@live.com> kirjoitti 4.3.2013 kello 21.23:
>> >
>> >> Hi,
>> >>
>> >> the ports in use are 2222 and 2223 for ssh, and 10000 up to 10019
>> >> (depends on how many are needed) for debugging.
>> >>
>> >> Port 65535 is not a valid port and should not be tunneled. QtCreator
>> >> shows this port when it cannot query the virtual machine for port
>> >> information for some reason.
>> >> So if you see port 65536 in QtCreator, then something went wrong and
>> >> that needs to found and fixed. Probably the recorded VBoxManage output
>> >> is not found or not played back correctly. Unfortunately, it's not
>> >> easy to debug this. I used strace on the QtCreator process a lot to
>> >> find out where it failed and how to make QtCreator happy with fake
>> >> data.
>> >>
>> >>
>> >> Regards,
>> >> Martin
>> >>
>> >>
>> >> 2013/3/4, Saija Eteläniemi <setel...@live.com>:
>> >>> Hi,
>> >>>
>> >>> Is there any listings which ports are used by the SDK?
>> >>> I'm running the SDK from a Mac host using Martin's instructions, but have
>> >>> trouble getting QtCreator to connect the Simulator. I tunneled the ports
>> >>> mentioned in Martin's post, and added 65535, seen from the QtCreator
>> >>> device
>> >>> settings, but it seems to be not enough. The terminal I login in Linux
>> >>> to my
>> >>> Mac host, I get an output: "channel 49: open failed: connect failed:
>> >>> Connection refused" when I the Test button in Devices page on QtCreator.
>> >>> Any idea if I'm just missing a port from my tunneling, or having some
>> >>> other
>> >>> problem I should check out?
>> >>>
>> >>> - Saija
>> >>> #matrixx
>> >>> @setelani
>> >>>
>> >>> Lähetetty iPadista
>> >>>
>> >>> "David Greaves" <setel...@live.com> kirjoitti 4.3.2013 kello
>> >>> 11.35:
>> >>>
>> >>>> Yes, and I'm afraid we don't have an easy workaround either.
>> >>>>
>> >>>> We'll fix it in QtCreator 'soon' and then you'll be able to compile your
>> >>>> own
>> >>>> version.
>> >>>>
>> >>>> I added it to known issues.
>> >>>>
>> >>>> David
>> >>>>
>> >>>> On 04/03/13 09:17, "Rücker, Thomas" wrote:
>> >>>>> Hi,
>> >>>>>
>> >>>>> known issue.
>> >>>>> see quote:
>> >>>>>
>> >>>>> On 26/02/13 17:09, David Greaves wrote:
>> >>>>>> On 26/02/13 09:02, "Rücker, Thomas" wrote:
>> >>>>>>> Hi,
>> >>>>>>>
>> >>>>>>> I decided to try to connect to my N950 running Nemo from the
>> >>>>>>> QtCreator
>> >>>>>>> of the
>> >>>>>>> Sailfish SDK.
>> >>>>>>> The problem is that something constantly resets the ssh port to
>> >>>>>>> '65535'.
>> >>>>>>> In the Wizzard (if you go through Mer device) it works for the
>> >>>>>>> initial
>> >>>>>>> connection test if you specify 22, but will create an entry as seen
>> >>>>>>> in
>> >>>>>>> the
>> >>>>>>> attached screenshot.
>> >>>>>> Thanks - yes, this looks like a bug.
>> >>>>>>
>> >>>>>> David
>> >>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> SailfishOS.org Devel mailing list
>> >>> _______________________________________________
>> >>> SailfishOS.org Devel mailing list
>> > _______________________________________________
>> > SailfishOS.org Devel mailing list
>> _______________________________________________
>> SailfishOS.org Devel mailing list
> _______________________________________________
> SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
