Closed a-m-s closed 1 year ago
Update .... I can't reproduce this from a native window cmd.exe terminal (npiperelay.exe parses the args fine), so it looks to be some WSL2 wonkiness, and yet "args" shows the command line so I don't know how that can be?
Almost certainly this issue: https://github.com/microsoft/WSL/issues/6170
Not npiperelay's fault; closing.
I installed "golang" in Ubuntu in WSL2, followed the cross-build instructions, and tried to run npiperelay.exe, but no matter what I do it just prints the usage message.
I tried modifying the source to see what's up and I find that "len(args)" is always the full number of command line parameters, including the executable name, and that none of the flag variables are set correctly.
I can't see how this can be something either you or I are doing wrong when "flag" is a library package and I'm just running it from bash in the usual way?
And yet, the only way I could get it to work is to hard code the values I want into the source (and then it works lovely, thanks).