On Tue, May 6, 2014 at 8:23 AM, zbenjamin
<1309...@bugs.launchpad.net>wrote:
> Thats a good question, my problem is not only to map the running
> emulators to the QtC settings, but also to map the not running
> emulators, like emu1 will be emulator1234 when its running.
>
> Of course i could use t
Thats a good question, my problem is not only to map the running
emulators to the QtC settings, but also to map the not running
emulators, like emu1 will be emulator1234 when its running.
Of course i could use the --port and store the used port inside QtC
settings. But that will fail as soon as so
As we discussed today at the IRC, it'd probably be better for us to just
export the --port argument in ubuntu-emulator, and let the SDK tool to
decide which port to use when starting the emulator. That way the SDK
itself can keep map the image with the running instance.
As we can't start 2 differe
Does returning a json solve you problem?
something like
ubuntu-emulator list --verbose
[
{
"arch": "armhf",
"adbPort": 8000,
"name": "myinstance",
"version": "302",
"extendedVersion": "ubuntu=.*,"
},
{
...
}
]
am I missing anything?
--
You received this bug notification be
Looking internally how the naming happens, it's basically a fixed socket
and adb host command that only allows the port itself to change from one
instance to another.
Without specifying any port when calling the emulator, it'll start at
5554 and increase +2 for every other instance, until it reach
