clang-build fails with "Illegal character in Path"

When I clang-build a VS Project, it fails for me with the following message (German Windows):

--- CLANG TIDY STARTED ---

Get-ChildItem : Illegales Zeichen im Pfad.
In C:\users\uid38621\appdata\local\microsoft\visualstudio\16.0_cec81720\extensions\z2xrjrot.1qu\Tooling\v1\clang-build.
ps1:545 Zeichen:12
+    $slns = Get-ChildItem -recurse -LiteralPath $pathToCheck -Filter " ...
+            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-ChildItem], ArgumentException
    + FullyQualifiedErrorId : System.ArgumentException,Microsoft.PowerShell.Commands.GetChildItemCommand
 
Cannot find given project(s)

--- CLANG TIDY FINISHED ---

I tracked down the issue to the following line of code:

https://github.com/Caphyon/clang-power-tools/blob/041844f6f3e1f3e11b4c5736eba8c38975cfaa49/ClangPowerTools/ClangPowerTools/Tooling/v1/clang-build.ps1#L545

I believe, this is due to adding \\?\ and running the command in PowerShell x86. While I can run the command in x64 Powershell, it fails in x86:

I literally just removed the code adding the \\?\ prefix for making it work:

https://github.com/Caphyon/clang-power-tools/blob/041844f6f3e1f3e11b4c5736eba8c38975cfaa49/ClangPowerTools/ClangPowerTools/Tooling/v1/clang-build.ps1#L538-L543

I didn’t draft a PR, as there is probably a reason for this code to exist. However it looks to me like it either needs to be removed, or the Addin must make sure it runs in x64 Powershell.

---

• Win 10 x64
• VS 2019
• Project configured with CMake
• Powershell 5

  Name                           Value
  ----                           -----
  PSVersion                      5.1.19041.2364
  PSEdition                      Desktop
  PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
  BuildVersion                   10.0.19041.2364
  CLRVersion                     4.0.30319.42000
  WSManStackVersion              3.0
  PSRemotingProtocolVersion      2.3
  SerializationVersion           1.1.0.1
  

[FlorianReimold]

Hi @mariru27

I tried it out, but it didn’t work:

[mariru27]

Hi @FlorianReimold,

Thank you for reporting this issue, and for provided information We are looking into it and working towards a fix. We will keep you updated as progress is made.

Best regards, Marina