I'm sorry for the slow response. I had to attend to some other things
first. It sounds like there's agreement to support multiple platform
instances, so I'll try to move things in that direction.
Further responses inline
On 20/01/2022 01:19, Greg Clayton wrote:
On Jan 19, 2022, at 4:28 AM,
> On Jan 19, 2022, at 4:28 AM, Pavel Labath wrote:
>
> On 19/01/2022 00:38, Greg Clayton wrote:
>> Platforms can contain connection specific setting and data. You might want
>> to create two different "remote-linux" platforms and connect each one to a
>> different remote linux machine. Each t
> On Jan 19, 2022, at 4:28 AM, Pavel Labath wrote:
>
> On 19/01/2022 00:38, Greg Clayton wrote:
>> Platforms can contain connection specific setting and data. You might want
>> to create two different "remote-linux" platforms and connect each one to a
>> different remote linux machine. Each t
On 19/01/2022 00:38, Greg Clayton wrote:
Platforms can contain connection specific setting and data. You might want to create two
different "remote-linux" platforms and connect each one to a different remote
linux machine. Each target which uses this platform would each be able to fetch files,
Platforms can contain connection specific setting and data. You might want to
create two different "remote-linux" platforms and connect each one to a
different remote linux machine. Each target which uses this platform would each
be able to fetch files, resolve symbol files, get OS version/build
Hello all,
currently our code treats platform name more-or-less as a unique
identifier (e.g. Platform::Find returns at most one platform instance
--the first one it finds).
This is why I was surprised that the "platform select" CLI command
always creates a new instance of the given platform
