Windows & MSVC support

[dcharkes]

Compilation on Windows with visual studio.

Closes:

• Windows & MSVC support #15

Some more details:

• Visual studio installations can be found with https://github.com/microsoft/vswhere.
• This PR basically automates https://learn.microsoft.com/en-us/cpp/build/walkthrough-compile-a-c-program-on-the-command-line?view=msvc-170
  • The compiler itself is cl.exe, there are two, one for each target architecture.
  • In order to have the right include paths etc, a vcvarsxxx.bat has to be invoked. We capture the environment variables by looking at set before and after the batch script invocation.

This PR contains a lot of .toFilePath() refactorings to ensure paths are handled correctly on Windows.

Also in this PR, the RelativePath tool resolver now takes globs instead of uri's so that we can resolve relative paths with /bla/*/ where * can be a version number for example.

[coveralls]

coverage: 99.919% (+0.02%) from 99.903%
when pulling f1702fe on windows
into ee1d836 on main.

[dcharkes]

Something iffy is going on with the code-paths on the Windows bot:

edit: An older build did the coverage correctly: https://coveralls.io/builds/59308648
commit: 8aaae0d
There was no change in the workflow between that commit and the current one.

Both builds have checked out the code in D:\a\native\native.
Running native\pkgs\c_compiler> dart pub global run coverage:test_with_coverage on Windows locally leads to pkgs\c_compiler\coverage\lcov.info with absolute paths and a pkgs\c_compiler\coverage\coverage.json with relative paths.

[HosseinYousefi]

LGTM! Thanks @dcharkes!

[dcharkes]

Thanks @HosseinYousefi

The current PR doesn't work on the Dart CI bots, because clang can't rely on std implementations being on path. We do have a std implementation in depot_tools and also an MSVC. However that MSVC doesn't have a vcvarsall.bat but some depot_tools specific script that sets the environment variables. I'll make a separate PR for that.