Ok, now I found my answer. DevShell library class must be included with StdLib in order to correctly process shell-style input parameters. Without it, it falls back on DevConsole
Thanks,
Tim
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Tim Lewis
Sent: Thursday, September 5, 2019 10:25 AM
To: devel@edk2.groups.io; afish@apple.com
Subject: Re: [edk2-devel] Mappings and StdLib
Andrew –
There is a standard call that provides this service, but I am porting over BSD utils to the shell and they just take a straight path and call open. So I want open to behave the way I expect it to. IN fact, the low level code separates out the “drive” from the path already, but the current library doesn’t add in the mappings into the list that gets created (it is used for stdin: stdout: and stderr:) The thing is that the underlying Shell APIs do handle this case, but the mapping is stripped before it gets to that layer.
Tim
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Andrew Fish via Groups.Io
Sent: Wednesday, September 4, 2019 5:35 PM
To: devel@edk2.groups.io; tim.lewis@insyde.com
Subject: Re: [edk2-devel] Mappings and StdLib
Tim,
I don't know about the plans with the StdLib, but I do remember a long time ago with the old shell there was a protocol that let you translate volume names (mappings) into handles and device paths.
So you could write a simple library that has 2 styles of APIs:
1) Handle + FilePath in Shell mapping with Volume Name out
2) Shell file path with mapping Volume names in and Simple File System handle Out with the file path
a) A device path out version of this is also useful
You can make the lib just error return if the Shell protocol does not exist so you don't make it a requirement. The caller handles that failure as the current working volume/directory case.
Thanks,
Andrew Fish