Currently our PowerShell build module has become a hard dependency to build PowerShell, as it generates the C# bindings from resource files (replacing resgen). This makes bootstrapping on platforms where we don't yet have PowerShell a pain (you have to generate the files elsewhere and bring them over).
It should be fairly straightforward to port this generation into a simple .NET Core project that our build script simply delegates to, bringing Start-PSBuild back to a convenience function (i.e. just runs a few cmake and dotnet commands).
I think this should be done sooner than later because bootstrapping on other platforms needs to be doable by the average developer.
/cc John W. Fawcett (@FawcettJohnW) sergei (@vors) A (@ealexjordan) Jason Shirk (@lzybkr)
Currently our PowerShell build module has become a hard dependency to build PowerShell, as it generates the C# bindings from resource files (replacing
resgen). This makes bootstrapping on platforms where we don't yet have PowerShell a pain (you have to generate the files elsewhere and bring them over).It should be fairly straightforward to port this generation into a simple .NET Core project that our build script simply delegates to, bringing
Start-PSBuildback to a convenience function (i.e. just runs a fewcmakeanddotnetcommands).I think this should be done sooner than later because bootstrapping on other platforms needs to be doable by the average developer.
/cc John W. Fawcett (@FawcettJohnW) sergei (@vors) A (@ealexjordan) Jason Shirk (@lzybkr)