On Tue, May 6, 2014 at 8:23 AM, zbenjamin <email address hidden>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 the --port and store the used port inside QtC
> settings. But that will fail as soon as someone starts a emulator
> outside of QtC, but QtC still will pick it up :/
>
I think we can do what we originally mentioned with a twist:
ubuntu-emulator create emulator # creates an instance with no preassigned
port
ubuntu-emulator run emulator # assigns a port to an emulator by checking
the available ports
ubuntu-emulator list --verbose # dumps a json; if the emulator is running
it will list a port, if not it won't
Of course I'll have to deal with the burden of stale files due to
killing/stopping the emulator in many different ways.
On Tue, May 6, 2014 at 8:23 AM, zbenjamin <email address hidden>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 the --port and store the used port inside QtC
> settings. But that will fail as soon as someone starts a emulator
> outside of QtC, but QtC still will pick it up :/
>
I think we can do what we originally mentioned with a twist:
ubuntu-emulator create emulator # creates an instance with no preassigned
port
ubuntu-emulator run emulator # assigns a port to an emulator by checking
the available ports
ubuntu-emulator list --verbose # dumps a json; if the emulator is running
it will list a port, if not it won't
Of course I'll have to deal with the burden of stale files due to
killing/stopping the emulator in many different ways.