You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently building MSMPI requires the WDK to be installed. As far as I can tell it is only required so that the MessageCompile command can be used in the project files. If that is true: would you accept a MR to replace using MessageCompile by some custom build command that directly calls mc.exe with the required arguments? As far as I know mc.exe is part of the Windows SDK and not the WDK, so this should be possible.
Not having to install the driver development kit only to build MSMPI would be especially interesting for builds in automated environments (e.g. vcpkg).
Currently building MSMPI requires the WDK to be installed. As far as I can tell it is only required so that the
MessageCompile
command can be used in the project files. If that is true: would you accept a MR to replace usingMessageCompile
by some custom build command that directly callsmc.exe
with the required arguments? As far as I knowmc.exe
is part of the Windows SDK and not the WDK, so this should be possible.Not having to install the driver development kit only to build MSMPI would be especially interesting for builds in automated environments (e.g.
vcpkg
).edit: I have added a simple patch in a MR to build MSMPI form source in vcpkg, that replaces the
MessageCompile
command by a simpleCustomBuild
command and allows to build MSMPI without the WDK being installed. See https://github.com/microsoft/vcpkg/blob/94aa80000a5e8770a1442990b2682d53156641a6/ports/msmpi/no-wdk.patch. Let me know if you would be interested in a MR proposing the same changes directly to MSMPI.The text was updated successfully, but these errors were encountered: