2 Commits

Include renames

Author	SHA1	Message	Date
Muhammad Danish	b4fd0468f6	Make WinGet config files consistent with new recommendations ... The new file naming conventions for WinGet configurations files are: - Use the `.winget` extension instead of `.dsc.yaml`. This allows user to run the configuration directly from the file explorer. - The configurations should be placed in a `.config` directory in the root of the repository. Reference: https://learn.microsoft.com/en-us/windows/package-manager/configuration/create#file-naming-convention This commit also removes `allowPrerelease: true` directive from the `Microsoft.WinGet.DSC` resource. The Microsoft.WinGet.DSC module is GA (stable) so the directive is no longer needed. See https://www.powershellgallery.com/packages/Microsoft.WinGet.DSC/ For reference, maintainers may see these recommendations enacted in the following Microsoft repositories: - WinGet CLI: https://github.com/microsoft/winget-cli/tree/master/.config - WinGet Packages: https://github.com/microsoft/winget-pkgs/tree/master/.config - WinGet Create: https://github.com/microsoft/winget-create/tree/main/.config - PowerToys: https://github.com/microsoft/PowerToys/tree/main/.config Change-Id: Ib88598f5fb93b1bb0ed1b608e0d690c196cf9b80 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/182675 Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com> Tested-by: Jenkins	2025-03-12 14:37:59 +01:00
Christian Lohmaier	ea6f4bb93e	winget configuration files for installing Visual Studio Community 2022 ... 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>	2024-10-10 23:49:19 +02:00