ea6f4bb93e
A first step into streamlining the dependency installation process using winget / DevHome You can apply winget configurations with DevHome or from commandline by running winget configure -f path-to-configuration.yaml The *.vsconfig files can also be manually imported into Visual Studio Installer to install missing components into an existing installation Two variants are provided in this commit, one set including the components needed to cross-compile for ARM64 (uses around 1GB) The version of the Windows SDK chosen is the one that matches the SDK from the recommended packages, to avoid installing two different SDKs when using the configuration that includes the recommended packages The *.vsconfig files don't include the implied packages/the ones required by the workload. For a list of the components and their corresponding friendly names, see https://learn.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-community Change-Id: Ie44ee3dd39c3e61fb2d7c597b71a4a81e0e6b8d3 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/173336 Tested-by: Jenkins Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
Symbolic link
1 line
No EOL
29 B
Text
Symbolic link
1 line
No EOL
29 B
Text
.configurations/2022.vsconfig |