feat: add MSBuild rule to build MSBuild projects.

[jsun-splunk]

This is an attempt to add a rule to build MSBuild project from bazel. This rule only supports MSBuild.exe from MSVC. dotnet msbuild is not supported.

MSBuild, aka Microsoft Build Engine is a platform for building applications. This engine provides an XML schema for a project file that controls how the build platform processes and builds software.

There are no source code to build from for MSBuild. There are also no prebuilt binaries that is available. Therefore, this rule is only availabe for pre-installed toolchain. This usually involves installing MSBuild along side MSVC.

MSBuild generates compile and link flags from project configuration and solution files. I have not been able to find a definitve way to override that so we can applied only the bazel generated flags. As a compromised, the generated bazel flags from cc_toolchain are added to a msbuild.props files and passed to MSBuild via the -p:ForceImportAfterCppTargets property. This at the minimum confirms bazel flags are applied.

[matt-sm]

I'm trying to picture how deps would work eg. msbuild with dep for rfcc/cc_library

[jsun-splunk]

I'm trying to picture how deps would work eg. msbuild with dep for rfcc/cc_library

wouldn't it be the same as other rules? i.e what you declare in out_shared_lib or out_static_lib become part of the CcInfo to be use downstream?

[matt-sm]

I'm trying to picture how deps would work eg. msbuild with dep for rfcc/cc_library

wouldn't it be the same as other rules? i.e what you declare in out_shared_lib or out_static_lib become part of the CcInfo to be use downstream?

I am thinking the other way - if msbuild had a dep on another ccinfo